Triple
T28030164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larkya La Pass |
E708242
|
entity |
| Predicate | crossingRequires |
P172807
|
FINISHED |
| Object | good acclimatization |
—
|
LITERAL FINISHED |
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: good acclimatization | Statement: [Larkya La Pass, crossingRequires, good acclimatization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossingRequires Context triple: [Larkya La Pass, crossingRequires, good acclimatization]
-
A.
crossingRequiredFor
Indicates that a particular crossing (such as a bridge, tunnel, or intersection) is necessary to move from one location or path to another.
-
B.
crossingOf
Indicates that one entity serves as the intersection or crossing point of two or more linear features, such as roads, paths, or tracks.
-
C.
crossingType
Indicates the specific kind or category of crossing (e.g., how or where one thing passes over, through, or across another).
-
D.
crossingOpened
Indicates that a crossing (such as a road, rail, or pedestrian crossing) has been opened or made available for passage.
-
E.
crossedByHighway
Indicates that a highway passes across or through the extent of a given entity or area.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 27, 2026, 8:15 p.m.