Triple
T12456771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ancient City of Aleppo |
E297679
|
entity |
| Predicate | addedToListInDanger |
P16739
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [Ancient City of Aleppo, addedToListInDanger, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addedToListInDanger Context triple: [Ancient City of Aleppo, addedToListInDanger, 2013]
-
A.
underDangerList
Indicates that an entity is classified as being on a designated danger or endangered list, signifying it is at risk or under threat.
-
B.
addedTo
Indicates that one entity has been included or incorporated into another entity, typically as a new component, member, or element.
-
C.
addedFor
Indicates that one entity was created, included, or introduced specifically for the benefit, use, or purpose of another entity.
-
D.
inDangerSince
Indicates that an entity has been in a state of danger continuously starting from a specified point in time.
-
E.
addedToListOfWorldHeritageInDanger
chosen
Indicates that a site has been officially placed on the List of World Heritage in Danger, recognizing it as threatened and in need of special protection or conservation measures.
- 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_69d6ada270808190b1a2b2e7b02bb426 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d95151e7348190a1d4953a8b416a13 |
completed | April 10, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69d94d3c27a08190a0237200203e476d |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:56 p.m.