Triple
T18544308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | magister equitum |
E453182
|
entity |
| Predicate | chiefLieutenantOf |
P132098
|
FINISHED |
| Object | Roman dictator |
—
|
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: Roman dictator | Statement: [magister equitum, chiefLieutenantOf, Roman dictator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chiefLieutenantOf Context triple: [magister equitum, chiefLieutenantOf, Roman dictator]
-
A.
chiefOfStaff
Indicates that one entity serves as the chief of staff for another entity, typically managing operations and coordinating activities on its behalf.
-
B.
chief
Indicates that one entity holds the highest-ranking leadership or authoritative position over another entity or within a specified context.
-
C.
chiefOfGeneralStaff
Indicates that a person holds the position of Chief of the General Staff in relation to a specific military organization or armed forces.
-
D.
chiefOfSecurity
Indicates that one entity holds the primary responsibility for overseeing and managing the security operations of another entity.
-
E.
chiefStrategist
Indicates that one entity serves as the primary planner and director of strategy for another entity.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534b935c48190a34b17eeae4fd583 |
completed | April 19, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:38 a.m.