Triple
T15683932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gnaeus Domitius Ahenobarbus (consul 122 BC) |
E377647
|
entity |
| Predicate | officeAfter |
P119744
|
FINISHED |
| Object | censor of the Roman Republic |
—
|
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: censor of the Roman Republic | Statement: [Gnaeus Domitius Ahenobarbus (consul 122 BC), officeAfter, censor of the Roman Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeAfter Context triple: [Gnaeus Domitius Ahenobarbus (consul 122 BC), officeAfter, censor of the Roman Republic]
-
A.
officeIn
Indicates that one entity has an office located within the premises or jurisdiction of another entity.
-
B.
officeUnder
Indicates that one office is subordinate to, managed by, or organizationally within the authority of another office.
-
C.
office
Indicates that an entity holds or occupies an official position, role, or post within an organization or institution.
-
D.
officeIsIn
Indicates that one office is located within or inside another specified place or building.
-
E.
officeStart
Indicates the time or date at which an entity’s term, role, or period of holding office begins.
- 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_69d85cd2e28481909d4e975bee20872f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04f31b5b881908e46ecd9fc6048ab |
completed | April 16, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69deda8c856c8190882330114f9a1a5f |
completed | April 15, 2026, 12:23 a.m. |
| PDg | Predicate description generation | batch_69dff7f3016c8190ac68d76e65e07af4 |
completed | April 15, 2026, 8:41 p.m. |
Created at: April 10, 2026, 4:17 a.m.