Triple
T7792206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEPTA Route 101 trolley |
E180205
|
entity |
| Predicate | routeLengthApprox |
P78936
|
FINISHED |
| Object | approximately 11 miles |
—
|
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 11 miles | Statement: [SEPTA Route 101 trolley, routeLengthApprox, approximately 11 miles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeLengthApprox Context triple: [SEPTA Route 101 trolley, routeLengthApprox, approximately 11 miles]
-
A.
approximateRouteLength
chosen
Indicates the estimated total distance or length of a given route, rather than its exact measured value.
-
B.
trailDistanceApprox
Indicates that the distance along a trail between two locations is approximately a specified value, allowing for some margin of error.
-
C.
approximateLengthInMiles
Indicates the estimated distance or extent of something measured in miles.
-
D.
trackLengthApproxKm
Indicates that one entity has an approximate track length, measured in kilometers, associated with it.
-
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_69ca827d22208190b4dc5aa680edcf5d |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae9111b2481909684a2d4aa4831c2 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:30 p.m.