Triple
T28046340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shingo La |
E708691
|
entity |
| Predicate | closestMajorRegion |
P139465
|
FINISHED |
| Object | Zanskar |
—
|
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: Zanskar | Statement: [Shingo La, closestMajorRegion, Zanskar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closestMajorRegion Context triple: [Shingo La, closestMajorRegion, Zanskar]
-
A.
nearestMajorState
Indicates the relationship where a given location is associated with the closest major state to it, typically by geographic distance.
-
B.
nearestMajorArea
chosen
Indicates the relationship where a given location is associated with the closest significant geographic or administrative area.
-
C.
shareMajorCityRegion
Indicates that two entities are associated with the same major city or its surrounding metropolitan region.
-
D.
isMajorRegionFor
Indicates that a region serves as a primary or significant area associated with a particular entity, activity, or phenomenon.
-
E.
nearestMajorCity
Indicates that one city is the closest significant urban center to another location or city compared to all other major cities.
- 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_69ef9b6cf538819094a633ffa67afec1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 27, 2026, 8:29 p.m.