Triple
T5540699
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walled City of Baku with the Shirvanshah's Palace and Maiden Tower |
E145279
|
entity |
| Predicate | underDangerList |
P65277
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Walled City of Baku with the Shirvanshah's Palace and Maiden Tower, underDangerList, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underDangerList Context triple: [Walled City of Baku with the Shirvanshah's Palace and Maiden Tower, underDangerList, true]
-
A.
inDangerSince
Indicates that an entity has been in a state of danger continuously starting from a specified point in time.
-
B.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
C.
threatToHumans
Indicates that the subject poses or represents a potential danger, harm, or risk to humans.
-
D.
endangerment
Indicates a relationship in which one entity exposes another to potential harm, risk, or danger.
-
E.
isVictimOf
Indicates that one entity suffers harm, loss, or wrongdoing as a result of another entity’s actions or events.
- F. None of above. chosen
Provenance (4 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_69c008fa64888190adae56c8f9ea4031 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01fc66cc08190b9b2a62098ecbdb1 |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0e72f08190bf705d8fe1639401 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f051e508190b3886d87b4afdd0b |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:35 p.m.