Triple
T25180522
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grimes Graves |
E630569
|
entity |
| Predicate | dateRangeStart |
P288
|
FINISHED |
| Object | around 3000 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 3000 BC | Statement: [Grimes Graves, dateRangeStart, around 3000 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateRangeStart Context triple: [Grimes Graves, dateRangeStart, around 3000 BC]
-
A.
startDateInYear
Indicates that an entity’s start date occurs within a specified calendar year.
-
B.
startDate
chosen
Indicates the point in time when an event, state, or relationship begins.
-
C.
calculationStartDate
Indicates the date on which a particular calculation or computation process begins.
-
D.
startDateConstraint
Indicates a restriction or condition placed on when something is allowed to start, typically specifying valid or required start dates.
-
E.
timePeriodAnalyzedStart
Indicates the starting point in time from which a given period is examined or analyzed.
- 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_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 12:35 p.m.