Triple
T626979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F train |
E15839
|
entity |
| Predicate | hasDirectionDesignation |
P15156
|
FINISHED |
| Object | Uptown/Queens-bound |
—
|
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: Uptown/Queens-bound | Statement: [F train, hasDirectionDesignation, Uptown/Queens-bound]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionDesignation Context triple: [F train, hasDirectionDesignation, Uptown/Queens-bound]
-
A.
hasTrafficDirection
Indicates that there is a specified flow or orientation of traffic associated with an entity (such as a road, lane, or route).
-
B.
hasRouteDirection
chosen
Indicates that a specified route is associated with a particular travel direction (e.g., inbound, outbound, northbound).
-
C.
hasDirectionVariability
Indicates that the direction associated with an entity or process is not fixed but varies over time, space, or conditions.
-
D.
hasDesignation
Indicates that an entity holds or is assigned a specific title, label, or formal designation.
-
E.
hasApproachRoad
Indicates that one entity is connected to or accessed by another entity via an approach road leading to it.
- 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49e587c448190987943a6aad209d1 |
completed | March 1, 2026, 8:15 p.m. |
| PD | Predicate disambiguation | batch_69a49d01b29081908be87e4cd7726ff1 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:35 p.m.