Triple
T31589849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Woodlawn station |
E806061
|
entity |
| Predicate | northTerminalForService |
P3375
|
FINISHED |
| Object | 4 train |
—
|
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: 4 train | Statement: [Woodlawn station, northTerminalForService, 4 train]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: northTerminalForService Context triple: [Woodlawn station, northTerminalForService, 4 train]
-
A.
terminusNortheast
Indicates that one entity serves as the northeastern terminus or endpoint of another entity (such as a route, line, or path).
-
B.
terminusNorth
chosen
Indicates that one entity serves as the northern endpoint or final stop of another entity, such as a route, line, or path.
-
C.
terminusDirection
Indicates the directional orientation or endpoint direction associated with a route, path, or line.
-
D.
westTerminalStation
Indicates that a station serves as the western terminal (end point) of a route, line, or service.
-
E.
direction2Terminus
Indicates the direction in which something leads toward or ends at a particular terminus or endpoint.
- 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_69f348d4891c8190b02bae3c8ecb68b7 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6abaa1f648190b77073771df3bf3b |
completed | May 3, 2026, 1:58 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 10:27 p.m.