Triple
T37633846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | At-Tur |
E936425
|
entity |
| Predicate | inDisputedTerritory |
P15542
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [At-Tur, inDisputedTerritory, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inDisputedTerritory Context triple: [At-Tur, inDisputedTerritory, yes]
-
A.
locatedInDisputedTerritory
chosen
Indicates that an entity is situated within a geographic area whose sovereignty or ownership is contested between two or more parties.
-
B.
associatedTerritoryDispute
Indicates that there is a territorial dispute or contested claim connected to the referenced entity or relationship.
-
C.
frontierDispute
Indicates a conflict or disagreement between entities over the location, control, or status of a shared boundary or border.
-
D.
appliesToTerritorialDisputes
Indicates that a rule, agreement, or condition is relevant to or governs situations involving territorial disputes between parties.
-
E.
loreConflict
Indicates that there is an inconsistency, contradiction, or incompatibility between pieces of lore or canonical information.
- 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_69f76ed31d8881908405da6c6d2f0463 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa1321b48190af92a3e7ec24ec5b |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba8860f98819080b7bab05837b974 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.