Triple
T24989811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-10 |
E625414
|
entity |
| Predicate | adjacentCodeDirectionWest |
P159711
|
FINISHED |
| Object | T-11 |
—
|
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: T-11 | Statement: [T-10, adjacentCodeDirectionWest, T-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentCodeDirectionWest Context triple: [T-10, adjacentCodeDirectionWest, T-11]
-
A.
adjacentRouteWest
Indicates that one route is directly adjacent to another on its western side.
-
B.
adjacentStationWest
Indicates that one station is immediately to the west of another station in a spatial or network layout.
-
C.
hasAdjacentStationDirectionNorthwest
Indicates that one station is directly adjacent to another in the northwest direction.
-
D.
adjacentStationTowardsSouth
Indicates that one station is directly next to another in the southward direction along a route or line.
-
E.
adjacentTimeZoneWest
Indicates that one time zone is directly to the west of another, sharing a common boundary without any other time zone in between.
- F. None of above. chosen
Provenance (4 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_69e2ff2611c081908710457fbe6d376b |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f5f7a205688190b8f36bff5013247c |
completed | May 2, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
| PDg | Predicate description generation | batch_69f5f6b32a8881909baa0db57b80d56a |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 18, 2026, 6:03 a.m.