Triple
T15469250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quintus Curtius Rufus |
E372112
|
entity |
| Predicate | possibleOfficeHeld |
P118355
|
FINISHED |
| Object | Roman senator (disputed) |
—
|
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 senator (disputed) | Statement: [Quintus Curtius Rufus, possibleOfficeHeld, Roman senator (disputed)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleOfficeHeld Context triple: [Quintus Curtius Rufus, possibleOfficeHeld, Roman senator (disputed)]
-
A.
electedOffice
Indicates that an entity holds or has held a particular office or position as a result of an election.
-
B.
stateOfPoliticalOffice
Indicates the political office or governmental position currently held or associated with an entity.
-
C.
isPoliticalOffice
Indicates that the subject is a formal governmental or political position held within a public institution or authority.
-
D.
representsOfficeOf
Indicates that one entity serves as the official office or administrative location associated with another entity.
-
E.
heldPoliticalOfficeIn
Indicates that an entity served in a political office or position within a specified governmental body or jurisdiction.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f6b49788190b270fdfe92646842 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded5deee00819099fa3e43313312e1 |
completed | April 15, 2026, 12:03 a.m. |
Created at: April 10, 2026, 3:33 a.m.