Triple
T20598181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Buller ski resort |
E506104
|
entity |
| Predicate | villageElevation |
P221
|
FINISHED |
| Object | approximately 1600 m |
—
|
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: approximately 1600 m | Statement: [Mount Buller ski resort, villageElevation, approximately 1600 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: villageElevation Context triple: [Mount Buller ski resort, villageElevation, approximately 1600 m]
-
A.
elevationAboveTown
Indicates that one location is situated at a higher elevation relative to a specified town.
-
B.
elevationAboveValley
Indicates the vertical height or altitude of an entity measured relative to the lowest point of the surrounding valley.
-
C.
elevationBy
Indicates a relationship where one entity raises, increases, or enhances the level, status, or intensity of another entity.
-
D.
valleyHeightAboveGround
Indicates the vertical distance between the valley’s lowest point and the surrounding ground level.
-
E.
elevation
chosen
Indicates the vertical height or altitude of one entity relative to a reference level or another 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa1e251c8190926dafe1402eb63c |
completed | April 20, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:40 a.m.