Triple
T8949588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Xia dynasty |
E213310
|
entity |
| Predicate | traditionalEndYear |
P82251
|
FINISHED |
| Object | c. 1600 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: c. 1600 BCE | Statement: [Xia dynasty, traditionalEndYear, c. 1600 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalEndYear Context triple: [Xia dynasty, traditionalEndYear, c. 1600 BCE]
-
A.
serializationEndYear
Indicates the year in which the serialization or serialized publication of an entity concluded.
-
B.
traditionalEnd
Indicates that one entity is the customary or historically established conclusion, outcome, or final stage of another entity or process.
-
C.
endYear
Indicates the year in which an event, state, or relationship comes to an end.
-
D.
endYearApprox
chosen
Indicates that the end year of an event, state, or relationship is known only approximately rather than as a precise calendar year.
-
E.
travelEndYear
Indicates the year in which a travel event or journey concludes.
- 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_69ca839843408190a39069a029a89f15 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc670b5f50819080f1c73992fe5281 |
completed | April 1, 2026, 12:30 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:59 p.m.