Triple
T27569673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nangpa Valley |
E695996
|
entity |
| Predicate | associatedPass |
P134381
|
FINISHED |
| Object | Nangpa La |
—
|
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: Nangpa La | Statement: [Nangpa Valley, associatedPass, Nangpa La]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPass Context triple: [Nangpa Valley, associatedPass, Nangpa La]
-
A.
associatedThrough
Indicates that two entities are connected or related to each other by means of a specified intermediary, context, or linkage.
-
B.
relatedPass
chosen
Indicates that one pass is associated with or connected to another pass in some relevant way.
-
C.
associatedFort
Indicates that one entity is connected or linked to a particular fort, typically as its related or corresponding fortification.
-
D.
associatedItem
Indicates that one item is linked or connected to another in a relevant or context-dependent way, without specifying a more precise relationship.
-
E.
associatedSingle
Indicates a one-to-one association where an entity is linked to exactly one corresponding related entity.
- 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_69ef53891af88190a193c5e2a1dac9b1 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_6a002103c93081908398fa5726f5fa6e |
completed | May 10, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_6a001fcb9fb48190a27d8f2ca983fbe6 |
completed | May 10, 2026, 6:03 a.m. |
Created at: April 27, 2026, 1:42 p.m.