Triple
T17599560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Tikitapu |
E428657
|
entity |
| Predicate | hasWalkingTrackLength |
P117419
|
FINISHED |
| Object | approximately 5.5 km |
—
|
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 5.5 km | Statement: [Lake Tikitapu, hasWalkingTrackLength, approximately 5.5 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWalkingTrackLength Context triple: [Lake Tikitapu, hasWalkingTrackLength, approximately 5.5 km]
-
A.
hasWalkingPathLength
chosen
Indicates the length or distance of a designated walking path associated with an entity.
-
B.
hasWalkingRouteType
Indicates that an entity is associated with a specific type or category of walking route (e.g., trail, path, or walking itinerary).
-
C.
mainTrackDistance
Indicates the distance measured along the primary or main track between two referenced points or entities.
-
D.
hasWalkingPathAround
Indicates that one entity has a walking path that encircles or runs around another entity.
-
E.
trailLengthApprox
Indicates an approximate measurement of the total length of a trail.
- 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_69d889e1c6148190ba76241e74688f8b |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46c4812d48190bf8e899fa8f7fbe4 |
completed | April 19, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fff0348190b899a32da537eaca |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:51 a.m.