Triple
T3088119
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plain of Jars |
E64422
|
entity |
| Predicate | estimatedDateRange |
P877
|
FINISHED |
| Object | c. 500 BCE–500 CE |
—
|
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. 500 BCE–500 CE | Statement: [Plain of Jars, estimatedDateRange, c. 500 BCE–500 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedDateRange Context triple: [Plain of Jars, estimatedDateRange, c. 500 BCE–500 CE]
-
A.
endTimeApproximate
Indicates that the recorded end time of an event or action is not exact but an approximate value.
-
B.
dateApproximate
chosen
Indicates that the associated date is not exact but estimated or approximate rather than precisely known.
-
C.
deliveryDate
Indicates the specific date on which a product, service, or item is scheduled or expected to be delivered.
-
D.
timePeriodEndApprox
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
E.
typicalEndDate
Indicates the date on which something, such as an event, process, or period, normally or customarily ends.
- 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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada209fd24819088d887de0a4158f4 |
completed | March 8, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69ad9ded78f881908be6fc0fb7c35764 |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:03 p.m.