Triple
T11304498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hell's Gate Airtram |
E267678
|
entity |
| Predicate | hasUpperStationElevation |
P46534
|
FINISHED |
| Object | about 300 metres above sea level |
—
|
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: about 300 metres above sea level | Statement: [Hell's Gate Airtram, hasUpperStationElevation, about 300 metres above sea level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpperStationElevation Context triple: [Hell's Gate Airtram, hasUpperStationElevation, about 300 metres above sea level]
-
A.
hasTopElevation
chosen
Indicates that an entity has a specified maximum or highest elevation value.
-
B.
hasAltitudeStation
Indicates that something is associated with or located at a station characterized by a specific altitude.
-
C.
hasElevationFeature
Indicates that one entity possesses or is characterized by a particular elevation-related feature or attribute, such as height, altitude, or vertical relief.
-
D.
hasHigherElevationArea
Indicates that one area is situated at a greater elevation above sea level than another area.
-
E.
hasLowerStation
Indicates that one entity occupies a lower rank, status, or position in a hierarchy relative to 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_69d6aaca5c24819083db46a30d86cb34 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e9a7255c81909675fe9ad6d71934 |
completed | April 9, 2026, 6:02 p.m. |
| PD | Predicate disambiguation | batch_69d787aa31888190860eecaa80da5b20 |
completed | April 9, 2026, 11:04 a.m. |
Created at: April 8, 2026, 9:32 p.m.