Triple
T9831162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mule Square |
E238984
|
entity |
| Predicate | distanceFromTrailhead_km |
P33049
|
FINISHED |
| Object | approximately 18 |
—
|
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 18 | Statement: [Mule Square, distanceFromTrailhead_km, approximately 18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromTrailhead_km Context triple: [Mule Square, distanceFromTrailhead_km, approximately 18]
-
A.
approximateRoundTripDistanceFromTrailhead
Indicates the estimated total distance of a complete out-and-back journey measured from the trailhead.
-
B.
trailDistanceApprox
Indicates that the distance along a trail between two locations is approximately a specified value, allowing for some margin of error.
-
C.
trackLengthApproxKm
Indicates that one entity has an approximate track length, measured in kilometers, associated with it.
-
D.
hikeLength
Indicates the distance or duration associated with a hiking activity or trail.
-
E.
lengthInKm
chosen
Indicates that one entity specifies the length or distance of another entity measured in kilometers.
- 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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb3297bd88190bf8c53a4ba00e0ae |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e30bc08190816c0a6d29c21b0f |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:32 p.m.