Triple
T7744503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Craggy Gardens |
E175591
|
entity |
| Predicate | parkwayMilepost |
P75083
|
FINISHED |
| Object | around milepost 364 |
—
|
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: around milepost 364 | Statement: [Craggy Gardens, parkwayMilepost, around milepost 364]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parkwayMilepost Context triple: [Craggy Gardens, parkwayMilepost, around milepost 364]
-
A.
nearbyHighwayMilepost
chosen
Indicates that one entity is located close to a specific highway milepost associated with another entity.
-
B.
trailMilepostOn
Indicates that a specific milepost is physically located on and associated with a particular trail segment or trail route.
-
C.
approximateMileMarker
Indicates an estimated or not precisely measured position along a route expressed in miles.
-
D.
crossesAtMilepost
Indicates that one entity crosses or intersects another at a specific milepost location.
-
E.
roadLength
Indicates the measured distance or extent of a road, typically expressed in units of length.
- 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_69c69960b3588190a53aa590d31d9544 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c70402169481909b219dc5f4a64b9b |
completed | March 27, 2026, 10:26 p.m. |
| PD | Predicate disambiguation | batch_69c7016c4a748190a7012030edaefcee |
completed | March 27, 2026, 10:15 p.m. |
Created at: March 27, 2026, 4:07 p.m.