Triple
T30092621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biddles Corner toll plaza |
E764775
|
entity |
| Predicate | isOnRouteDirection |
P15156
|
FINISHED |
| Object | north–south |
—
|
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: north–south | Statement: [Biddles Corner toll plaza, isOnRouteDirection, north–south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnRouteDirection Context triple: [Biddles Corner toll plaza, isOnRouteDirection, north–south]
-
A.
isInTravelDirection
Indicates that one entity lies along or matches the direction in which another entity is traveling or moving.
-
B.
hasRouteDirection
chosen
Indicates that a specified route is associated with a particular travel direction (e.g., inbound, outbound, northbound).
-
C.
isInDirectionOf
Indicates that one entity is oriented or positioned toward the direction in which another entity lies.
-
D.
isPartOfRoute
Indicates that something (such as a segment, stop, or step) belongs to and is contained within a larger route.
-
E.
isRouteOn
Indicates that one route is located on, follows along, or is aligned with another specified path or infrastructure.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f67d8dc1988190835bb2ef7bf4f8b7 |
completed | May 2, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:06 p.m.