Triple
T25180523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grimes Graves |
E630569
|
entity |
| Predicate | dateRangeEnd |
P9332
|
FINISHED |
| Object | around 1900 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: around 1900 BC | Statement: [Grimes Graves, dateRangeEnd, around 1900 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateRangeEnd Context triple: [Grimes Graves, dateRangeEnd, around 1900 BC]
-
A.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
B.
timePeriodEndApprox
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
C.
endDateOfEntries
Indicates the date on which the referenced entries conclude or are no longer valid.
-
D.
rangeEnd
chosen
Indicates the endpoint or upper boundary value of a specified range in a relationship or measurement.
-
E.
earlierMPEndDate
Indicates that the end date of one Member of Parliament’s term occurs earlier in time than the end date of another Member of Parliament’s term.
- 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46dc5e4b08190a2638f941be1aaeb |
completed | May 1, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 12:35 p.m.