Triple
T35861960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gnaeus Pompeius Magnus (consul of AD 55) |
E1036974
|
entity |
| Predicate | RomanOfficeHeld |
P131804
|
FINISHED |
| Object | consulship of AD 55 |
—
|
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: consulship of AD 55 | Statement: [Gnaeus Pompeius Magnus (consul of AD 55), RomanOfficeHeld, consulship of AD 55]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RomanOfficeHeld Context triple: [Gnaeus Pompeius Magnus (consul of AD 55), RomanOfficeHeld, consulship of AD 55]
-
A.
RomanRepresentative
Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation to another entity.
-
B.
ruledByOffice
Indicates that an entity is governed or administered by a particular official position or office.
-
C.
allyOfRome
Indicates a relationship where one entity is politically or militarily aligned with, and offers support or cooperation to, Rome.
-
D.
officeHolderTitleInLatin
Indicates that the specified office holder’s title is expressed in its Latin-language form.
-
E.
officeHoldersWere
chosen
Indicates that certain individuals held specific offices or positions during a particular time or context.
- 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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:06 p.m.