Triple
T32444748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolwaling |
E829111
|
entity |
| Predicate | hasHighPass |
P197208
|
FINISHED |
| Object | Tashi Lapcha 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: Tashi Lapcha Pass | Statement: [Rolwaling, hasHighPass, Tashi Lapcha Pass]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighPass Context triple: [Rolwaling, hasHighPass, Tashi Lapcha Pass]
-
A.
hasHigh
Indicates that an entity possesses a high level, degree, or intensity of a specified attribute or property.
-
B.
hasHighPropertyValues
Indicates that the associated entity possesses property values that are above a defined or typical threshold.
-
C.
hasHighMass
Indicates that an entity possesses a mass that is large or above a specified threshold relative to a given standard or context.
-
D.
highestPass
Indicates that an entity has achieved the greatest passing value, score, or level among a set of compared entities.
-
E.
hasHighest
Indicates that one entity possesses the greatest value, rank, or level in a specified attribute or set compared to all others.
- 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_69f3491d2e5c819092b1c9535beff8ec |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe7bfc94bc81909eeec946e8c1c450 |
completed | May 9, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69fe7b74a1188190886f128e07f712da |
completed | May 9, 2026, 12:10 a.m. |
| PDg | Predicate description generation | batch_69fe7bfb71b08190bed5c33e4ab7afff |
completed | May 9, 2026, 12:12 a.m. |
Created at: May 1, 2026, 12:55 a.m.