Triple
T2730391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Tongariro |
E60297
|
entity |
| Predicate | hasLengthOfMainTrail |
P18078
|
FINISHED |
| Object | approximately 19.4 kilometres (Tongariro Alpine Crossing) |
—
|
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 19.4 kilometres (Tongariro Alpine Crossing) | Statement: [Mount Tongariro, hasLengthOfMainTrail, approximately 19.4 kilometres (Tongariro Alpine Crossing)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLengthOfMainTrail Context triple: [Mount Tongariro, hasLengthOfMainTrail, approximately 19.4 kilometres (Tongariro Alpine Crossing)]
-
A.
hasTrailLength
Indicates that an entity (such as a trail or route) has a specific measured length.
-
B.
hasMainStraightLengthKm
Indicates the length in kilometers of the primary or main straight segment associated with an entity.
-
C.
trailLengthApprox
chosen
Indicates an approximate measurement of the total length of a trail.
-
D.
hasTrail
Indicates that an entity possesses, includes, or is associated with a trail or pathway.
-
E.
mainStraightLengthM
Indicates the length, measured in meters, of the main straight segment (typically of a track, road, or similar linear feature).
- 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_69ab4b75cd908190b691ef0d1801acda |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdaeca6208190a586afb00747146a |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd82586f88190a98f60d3247fe2d3 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.