Triple
T696684
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old City of Jerusalem UNESCO World Heritage Site |
E13908
|
entity |
| Predicate | wallConstructionPeriod |
P3543
|
FINISHED |
| Object | 16th century |
—
|
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: 16th century | Statement: [Old City of Jerusalem UNESCO World Heritage Site, wallConstructionPeriod, 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wallConstructionPeriod Context triple: [Old City of Jerusalem UNESCO World Heritage Site, wallConstructionPeriod, 16th century]
-
A.
constructionTime
chosen
Indicates the duration or specific point in time required to construct or build an entity.
-
B.
constructionStartYear
Indicates the calendar year in which the construction of something was begun.
-
C.
reconstructionYear
Indicates the year in which something was rebuilt, restored, or reconstructed after damage, alteration, or destruction.
-
D.
demolitionPeriod
Indicates the time span during which the demolition of an entity or structure takes place.
-
E.
reconstructionOrRestorationDate
Indicates the date on which an entity was reconstructed or restored after damage, alteration, or deterioration.
- 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_69a493406c408190957eeec9048a8fb6 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a0c8055881909565ebde2be8fd7a |
completed | March 1, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69a49d2586b081908e052cc5ba1d2685 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.