Triple
T10034827
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peak 2 Peak Gondola |
E204939
|
entity |
| Predicate | unsupportedSpanLength |
P4063
|
FINISHED |
| Object | 3019 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: 3019 metres | Statement: [Peak 2 Peak Gondola, unsupportedSpanLength, 3019 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unsupportedSpanLength Context triple: [Peak 2 Peak Gondola, unsupportedSpanLength, 3019 metres]
-
A.
largestSpan
Indicates that the referenced entity has the greatest extent or coverage (in distance, time, or range) among a set of comparable spans.
-
B.
properLengthMeasuredIn
Indicates that the proper (intrinsic or rest-frame) length of an entity is expressed using a specified unit of measurement.
-
C.
numberOfSpans
Indicates the total count of distinct spans or segments associated with an entity or within a specified context.
-
D.
supportsTagLength
Indicates that an entity is capable of handling or enforcing a specified tag length.
-
E.
hasMainSpanLength
chosen
Indicates the relationship specifying the primary or main span’s length associated with an 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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdce4a515c8190baec86d924623b12 |
completed | April 2, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:55 p.m.