Triple
T17419761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bab al-Amud |
E423579
|
entity |
| Predicate | rebuiltAroundYear |
P9623
|
FINISHED |
| Object | 1537 |
—
|
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: 1537 | Statement: [Bab al-Amud, rebuiltAroundYear, 1537]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rebuiltAroundYear Context triple: [Bab al-Amud, rebuiltAroundYear, 1537]
-
A.
reconstructionYear
chosen
Indicates the year in which something was rebuilt, restored, or reconstructed after damage, alteration, or destruction.
-
B.
rebuiltInCentury
Indicates that an existing structure or entity was reconstructed or significantly rebuilt during a specified century.
-
C.
rebuiltOn
Indicates that one entity has been reconstructed, restored, or built again on, over, or using the foundation, structure, or basis of another entity.
-
D.
reconstructionOrRestorationDate
Indicates the date on which an entity was reconstructed or restored after damage, alteration, or deterioration.
-
E.
rebuiltBetween
Indicates that an entity was reconstructed or rebuilt during a time interval bounded by two specified temporal points.
- 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e44236419c8190a106748bca6f30cd |
completed | April 19, 2026, 2:47 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:46 a.m.