Triple
T6178217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple of Virtus |
E137873
|
entity |
| Predicate | dedicatedToConcept |
P69507
|
FINISHED |
| Object | courage |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: courage | Statement: [Temple of Virtus, dedicatedToConcept, courage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dedicatedToConcept Context triple: [Temple of Virtus, dedicatedToConcept, courage]
-
A.
oftenDedicatedTo
Indicates that something is frequently or habitually devoted, assigned, or committed to a particular purpose, activity, or recipient.
-
B.
dedicated
Indicates that one entity is formally assigned, reserved, or committed for the specific use, benefit, or purpose of another entity.
-
C.
dedicationType
Indicates the specific kind or category of dedication that characterizes the relationship or action between entities.
-
D.
dedicatee
Indicates the person or entity to whom a work, such as a book, artwork, or performance, is formally dedicated.
-
E.
dedicationBy
Indicates that one entity formally dedicates, commits, or devotes another entity (such as a work, resource, or effort) to a particular person, purpose, or cause.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69c008a80f748190ba3d07ffc81acb29 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05dc9f3d88190ab46b3b246f5a8df |
completed | March 22, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c87340819088003f427706ebf8 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:18 p.m.