Triple
T11304499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hell's Gate Airtram |
E267678
|
entity |
| Predicate | hasVerticalInterval |
P86534
|
FINISHED |
| Object | approximately 150 metres |
—
|
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 150 metres | Statement: [Hell's Gate Airtram, hasVerticalInterval, approximately 150 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVerticalInterval Context triple: [Hell's Gate Airtram, hasVerticalInterval, approximately 150 metres]
-
A.
hasInterval
Indicates that something is associated with a specific span or range between two points in time, space, or value.
-
B.
hasContourInterval
chosen
Indicates that one entity specifies the vertical distance between contour lines represented by another entity.
-
C.
hasRange
Indicates that a property or relation is constrained to take its values from a specified class, type, or value set.
-
D.
invariantInterval
Indicates that a certain interval or range remains unchanged or constant under a specified transformation or set of conditions.
-
E.
hasPeriodRange
Indicates that there is a temporal span or interval during which something is valid, active, or applicable.
- 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.