Triple
T7505537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chanhudaro |
E177377
|
entity |
| Predicate | estimatedEndDate |
P35259
|
FINISHED |
| Object | circa 1700 BCE |
—
|
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: circa 1700 BCE | Statement: [Chanhudaro, estimatedEndDate, circa 1700 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedEndDate Context triple: [Chanhudaro, estimatedEndDate, circa 1700 BCE]
-
A.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
B.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
-
C.
timePeriodEndApprox
chosen
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
D.
deFactoEndDate
Indicates the date on which a relationship, status, or condition effectively ended in practice, regardless of any formal or official end date.
-
E.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
- 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_69c69f276b108190af2cc790b6554544 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f5b5fcd88190ab4ab0ba96a6aa4b |
completed | March 27, 2026, 9:25 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d44e9481909813e073b194f6f4 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:44 p.m.