Triple
T284538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Republic |
E5859
|
entity |
| Predicate | highestOffice |
P2716
|
FINISHED |
| Object | consul |
—
|
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: consul | Statement: [Roman Republic, highestOffice, consul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestOffice Context triple: [Roman Republic, highestOffice, consul]
-
A.
electedOffice
Indicates that an entity holds or has held a particular office or position as a result of an election.
-
B.
officeHolderOf
Indicates that a person holds or has held an official position or role within a specified organization, institution, or office.
-
C.
oneOfTheGreatOfficesOfState
chosen
Indicates that the entity holds or pertains to one of the highest-ranking senior government positions traditionally recognized as the Great Offices of State.
-
D.
firstOfficeHolder
Indicates that the subject is the very first individual to hold a particular office or position associated with the object.
-
E.
headOfGovernment
Indicates that one entity serves as the chief executive authority or leader of the government of 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_69a25946a7ac8190a78871c210213272 |
completed | Feb. 28, 2026, 2:56 a.m. |
| NER | Named-entity recognition | batch_69a25e2aba74819093eddd8d820260c0 |
completed | Feb. 28, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69a25b795a6c8190944d48e8418e0ccd |
completed | Feb. 28, 2026, 3:05 a.m. |
Created at: Feb. 28, 2026, 3:02 a.m.