Triple
T9779001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ziggurat of Ur |
E237317
|
entity |
| Predicate | builtInCenturyBCE |
P11259
|
FINISHED |
| Object | 21st century 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: 21st century BCE | Statement: [Ziggurat of Ur, builtInCenturyBCE, 21st century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtInCenturyBCE Context triple: [Ziggurat of Ur, builtInCenturyBCE, 21st century BCE]
-
A.
approximateBirthCenturyBCE
Indicates that an entity’s birth is estimated to have occurred within a specified century before the Common Era (BCE), rather than on an exact year or date.
-
B.
approximateStartCenturyBC
chosen
Indicates that an entity’s starting time or occurrence is approximately located within a specified century before the Common Era (BC).
-
C.
approximateUseEndCenturyBC
Indicates an estimated century BCE by which the use or activity associated with the subject is believed to have ended.
-
D.
dateToCenturyBCE
Indicates the mapping of a specific calendar date to the century before the Common Era (BCE) in which that date falls.
-
E.
endedInCentury
Indicates that an event, period, or process concluded during a specified century.
- 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_69ca84d975a08190aab25b02a89bdab3 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda13663f081909b95563038eb6485 |
completed | April 1, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69cd03d77c6c81909b675955bf113320 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:27 p.m.