Triple
T35150606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohinewai |
E1014975
|
entity |
| Predicate | hasTransportRouteNearby |
P96747
|
FINISHED |
| Object | State Highway 1 |
—
|
NE NERFINISHED |
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: State Highway 1 | Statement: [Ohinewai, hasTransportRouteNearby, State Highway 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTransportRouteNearby Context triple: [Ohinewai, hasTransportRouteNearby, State Highway 1]
-
A.
hasTransportationProximityTo
Indicates that one entity is located near or conveniently accessible to another entity in terms of transportation options or routes.
-
B.
hasTransportRoute
Indicates that there exists a designated transportation connection or route linking one entity to another.
-
C.
hasPublicTransitRoute
Indicates that there exists a public transportation route (such as a bus, train, or tram line) connecting or serving the related entities.
-
D.
hasNearbyTransportationCorridor
chosen
Indicates that an entity is located close to a significant transportation route or corridor, such as a road, railway, or transit line.
-
E.
hasNearbyWalkingRoutes
Indicates that there are walkable paths or routes located close to the referenced entity.
- 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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff9e91bba08190af04b31ad815b13a |
completed | May 9, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69ff9e00e4808190bde8f07e6519a72c |
completed | May 9, 2026, 8:50 p.m. |
Created at: May 3, 2026, 4:02 p.m.