Triple
T2083984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kashmir conflict |
E45305
|
entity |
| Predicate | consideredFlashpointBy |
P35709
|
FINISHED |
| Object | international observers |
—
|
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: international observers | Statement: [Kashmir conflict, consideredFlashpointBy, international observers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: consideredFlashpointBy Context triple: [Kashmir conflict, consideredFlashpointBy, international observers]
-
A.
notableFire
Indicates that a significant or historically important fire event is associated with the subject.
-
B.
hasEternalFlame
Indicates that an entity possesses or maintains a flame that is intended to burn perpetually without being extinguished.
-
C.
followsInCanon
Indicates that one entity occurs later than and in continuity with another within an established narrative or canonical sequence.
-
D.
blindedBy
Indicates that one entity causes another to lose the ability to see or perceive clearly, either literally or metaphorically.
-
E.
notableExposure
Indicates that an entity has received significant public attention, visibility, or coverage, making it notably exposed or recognized.
- 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_69a8891869c88190a02643e3bb746f59 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abba524b60819089a11957ce6dbc4b |
completed | March 7, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69abb7b298a48190b4bdf7c9800b058d |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb94ec400819097596732aabed854 |
completed | March 7, 2026, 5:36 a.m. |
Created at: March 4, 2026, 7:41 p.m.