Triple
T30501255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashur (Qal'at Sherqat) |
E776141
|
entity |
| Predicate | dateOfEntryOnListInDanger |
P63186
|
FINISHED |
| Object | 2003 |
—
|
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: 2003 | Statement: [Ashur (Qal'at Sherqat), dateOfEntryOnListInDanger, 2003]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfEntryOnListInDanger Context triple: [Ashur (Qal'at Sherqat), dateOfEntryOnListInDanger, 2003]
-
A.
endangeredListingYear
chosen
Indicates the year in which an entity was officially designated or listed as endangered.
-
B.
listedAsEndangeredBy
Indicates that an entity is classified as endangered according to the assessment or designation made by a specified authority or organization.
-
C.
threatenedWhen
Indicates that one entity is in a state of being threatened or under threat during a specific time or under certain conditions associated with another entity or event.
-
D.
isEndangeredDueTo
Indicates that an entity is endangered as a result of the specific cause or factor represented by the related entity.
-
E.
entryDate
Indicates the date on which an entity was first recorded, created, or entered into a system or context.
- 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7979a073881909a4fde2558e6b6f3 |
completed | May 3, 2026, 6:44 p.m. |
| PD | Predicate disambiguation | batch_69f7961550f88190b7bb8a9155458b54 |
completed | May 3, 2026, 6:38 p.m. |
Created at: April 29, 2026, 8:14 p.m.