Triple
T4558851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman lictor |
E120544
|
entity |
| Predicate | numberForCuruleAedile |
P57666
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [Roman lictor, numberForCuruleAedile, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberForCuruleAedile Context triple: [Roman lictor, numberForCuruleAedile, 2]
-
A.
ordinalNumberAsEmperor
Indicates the numerical order in which a person held the title or role of emperor.
-
B.
hasNumberOfAugusti
Indicates the number of Augusti (co-emperors or senior emperors) associated with a given entity or context.
-
C.
RomanRepresentative
Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation to another entity.
-
D.
rankInRomanEast
Indicates that one entity holds a specific rank or position within the administrative, military, or social hierarchy of the Roman East relative to another entity or context.
-
E.
numberOfConsulships
Indicates the total count of times an entity has held the office or role of consul.
- 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_69bd4636f1648190a701445c2fcd9c17 |
completed | March 20, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69bd5829cc34819086ad2ae58446502e |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56f6e75481909c487a94a2c2d0ba |
completed | March 20, 2026, 2:17 p.m. |
Created at: March 20, 2026, 1:09 p.m.