Triple
T9308809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman triumphs |
E223955
|
entity |
| Predicate | honoreeTitle |
P43861
|
FINISHED |
| Object | triumphator |
—
|
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: triumphator | Statement: [Roman triumphs, honoreeTitle, triumphator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: honoreeTitle Context triple: [Roman triumphs, honoreeTitle, triumphator]
-
A.
honoreeRole
chosen
Indicates the specific role, title, or capacity in which an individual is being honored in relation to an award, event, or recognition.
-
B.
honoursTitle
Indicates that an entity holds or is designated by a formal honorific or honorary title.
-
C.
honorificTitle
Indicates that one entity serves as a formal honorific or respectful title used to address or refer to another entity.
-
D.
honoreeKnownFor
Indicates that an honoree is recognized or celebrated specifically for a particular work, achievement, contribution, or notable attribute.
-
E.
awardsTitle
Indicates that an entity confers or grants a specific title or honorific designation to another entity.
- F. None of above.
Provenance (3 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_69ca8424d0f08190831e2e93c6533aeb |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd1daba67c819081d53545d67ef127 |
completed | April 1, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69cc7a61e9a4819096eb014f3791ef2e |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:37 p.m.