Triple
T29575506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalapani region |
E753431
|
entity |
| Predicate | relatedDisputedArea |
P62867
|
FINISHED |
| Object | Lipulekh Pass |
—
|
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: Lipulekh Pass | Statement: [Kalapani region, relatedDisputedArea, Lipulekh Pass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedDisputedArea Context triple: [Kalapani region, relatedDisputedArea, Lipulekh Pass]
-
A.
nearbyDisputedArea
Indicates that an entity is located close to a geographic area whose ownership, control, or boundaries are contested.
-
B.
associatedTerritoryDispute
chosen
Indicates that there is a territorial dispute or contested claim connected to the referenced entity or relationship.
-
C.
locatedInDisputedTerritory
Indicates that an entity is situated within a geographic area whose sovereignty or ownership is contested between two or more parties.
-
D.
borderDisputesWith
Indicates that there are contested or unresolved boundary claims between two entities.
-
E.
disputed
Indicates that there is active disagreement or contestation over the validity, ownership, interpretation, or status of the relationship or claim between the entities.
- 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_69f0ef80bf8c8190ad286e99f7df0c63 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_6a017114e7148190b7479284c316443d |
completed | May 11, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_6a016eebd60481909212e2a49ef95fbe |
completed | May 11, 2026, 5:53 a.m. |
Created at: April 28, 2026, 6:02 p.m.