Triple
T571923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts Route 16 |
E13680
|
entity |
| Predicate | hasDirectionA |
P15156
|
FINISHED |
| Object | West |
—
|
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: West | Statement: [Massachusetts Route 16, hasDirectionA, West]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionA Context triple: [Massachusetts Route 16, hasDirectionA, West]
-
A.
hasRouteDirection
chosen
Indicates that a specified route is associated with a particular travel direction (e.g., inbound, outbound, northbound).
-
B.
hasTrafficDirection
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
C.
frontLineDirection
Indicates the primary orientation or bearing in which the front line of a conflict, formation, or boundary is facing or advancing.
-
D.
primaryDirection
Indicates the main or dominant directional orientation associated with an entity or relation.
-
E.
powerDirection
Indicates the direction in which power, influence, or control flows from one entity to another.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49b49bad88190bc73d31a317c0ef4 |
completed | March 1, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_69a494c2caac819086ab316fa49d324c |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.