Triple
T2984637
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gnaeus Domitius Ahenobarbus |
E80591
|
entity |
| Predicate | time period |
P302
|
FINISHED |
| Object | 1st century BC |
—
|
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: 1st century BC | Statement: [Gnaeus Domitius Ahenobarbus, time period, 1st century BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: time period Context triple: [Gnaeus Domitius Ahenobarbus, time period, 1st century BC]
-
A.
timePeriod
chosen
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
B.
time
Indicates a temporal relationship specifying when an event occurs or how entities are ordered or related in time.
-
C.
timePeriodProposed
Indicates that a specific time period has been suggested or put forward for consideration or adoption.
-
D.
timePeriodImplied
Indicates that a time period is inferred or implied by context rather than being explicitly specified.
-
E.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
- 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_69ad8b16c3488190b47b6aa7a59a335b |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99c65ad0819087bb4ae92ab0dc55 |
completed | March 8, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ad9611fc348190a5d17d237f653f60 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.