Triple
T9267214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohio Drive SW |
E222729
|
entity |
| Predicate | hasDirectionQualifier |
P65355
|
FINISHED |
| Object | Southwest (SW) |
—
|
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: Southwest (SW) | Statement: [Ohio Drive SW, hasDirectionQualifier, Southwest (SW)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionQualifier Context triple: [Ohio Drive SW, hasDirectionQualifier, Southwest (SW)]
-
A.
hasDirectionType
Indicates that something possesses or is associated with a specific type or category of direction.
-
B.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
C.
hasDirectionReference
chosen
Indicates that one entity specifies or points to a directional orientation or reference frame for another entity.
-
D.
hasDirectionVariant
Indicates that one entity is a directional variant or orientation-specific form of another entity.
-
E.
hasRouteDirection
Indicates that a specified route is associated with a particular travel direction (e.g., inbound, outbound, northbound).
- 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_69ca841f2e808190a64f4c31903a1332 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd074bac9481909419988a9e8d9bd5 |
completed | April 1, 2026, 11:53 a.m. |
| PD | Predicate disambiguation | batch_69cc7a537bbc8190baee71f556e52a7b |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:33 p.m.