Triple
T35861943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gnaeus Pompeius Magnus (consul of AD 55) |
E1036974
|
entity |
| Predicate | officeStartEra |
P1383
|
FINISHED |
| Object | AD |
—
|
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: AD | Statement: [Gnaeus Pompeius Magnus (consul of AD 55), officeStartEra, AD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeStartEra Context triple: [Gnaeus Pompeius Magnus (consul of AD 55), officeStartEra, AD]
-
A.
officeStartCentury
Indicates the century in which an entity’s period of holding office or official position began.
-
B.
officeStartApproximate
Indicates that the start of a person’s term in office is known only approximately, not as an exact date.
-
C.
officeStart
chosen
Indicates the time or date at which an entity’s term, role, or period of holding office begins.
-
D.
officeStartFor
Indicates the time or date at which an entity begins its term, role, or period of service in an office or official position.
-
E.
officeStartAfter
Indicates that one entity’s term or period in office begins after another specified time or event.
- 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_69fffc783b648190bcd7df017514d206 |
completed | May 10, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69fffc03fa24819099e12413dc6e0afd |
completed | May 10, 2026, 3:31 a.m. |
Created at: May 3, 2026, 4:06 p.m.