Triple
T36137129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chang Chenmo Valley |
E1045197
|
entity |
| Predicate | borderStateBefore2019 |
P16110
|
FINISHED |
| Object | Jammu and Kashmir |
—
|
NE NERFINISHED |
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: Jammu and Kashmir | Statement: [Chang Chenmo Valley, borderStateBefore2019, Jammu and Kashmir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderStateBefore2019 Context triple: [Chang Chenmo Valley, borderStateBefore2019, Jammu and Kashmir]
-
A.
stateBefore2019
Indicates that a particular state, condition, or configuration held true prior to the year 2019.
-
B.
borderStateOf
Indicates that one state shares a common boundary or border with another state.
-
C.
borderRegime
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
-
D.
becameInternationalBorderInYear
Indicates that a boundary between entities started functioning as an international border in the specified year.
-
E.
borderHistory
chosen
Indicates the historical changes, events, or status of borders between entities over time.
- 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_69f76e36a4508190b5bfc8f594272a4c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffc89596d08190b97bd60b45c7f9c0 |
completed | May 9, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69ffc81ba5dc8190ae94d44e2284948f |
completed | May 9, 2026, 11:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.