Triple
T31924606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purling Brook Falls |
E815066
|
entity |
| Predicate | walkingTrackLength |
P57550
|
FINISHED |
| Object | approximately 4 kilometres for main circuit |
—
|
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 4 kilometres for main circuit | Statement: [Purling Brook Falls, walkingTrackLength, approximately 4 kilometres for main circuit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: walkingTrackLength Context triple: [Purling Brook Falls, walkingTrackLength, approximately 4 kilometres for main circuit]
-
A.
walkingTrack
Indicates a designated path or route intended for people to walk along for exercise, leisure, or transit.
-
B.
mainTrackDistance
chosen
Indicates the distance measured along the primary or main track between two referenced points or entities.
-
C.
tourLength
Indicates the total duration or distance covered by a tour or route.
-
D.
lapLengthOfTrack
Indicates the distance or length of a single lap around a track.
-
E.
trailDistanceContext
Indicates the contextual distance or separation between entities along a trail, path, or route.
- 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_69f348f1df848190851bbfb988da3414 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b1fabffc81909d345f47c6692073 |
completed | May 3, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69f6aca7081881909e96a8b05ec086bb |
completed | May 3, 2026, 2:02 a.m. |
Created at: May 1, 2026, 12:03 a.m.