Triple
T21715596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JY13 |
E536018
|
entity |
| Predicate | adjacentStationCodePrevious |
P66132
|
FINISHED |
| Object | JY12 |
—
|
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: JY12 | Statement: [JY13, adjacentStationCodePrevious, JY12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentStationCodePrevious Context triple: [JY13, adjacentStationCodePrevious, JY12]
-
A.
precedingStation
chosen
Indicates that one station is located immediately before another station in a route or sequence.
-
B.
precedingStationTowards
Indicates that one station is immediately before another station along a specified direction or route toward a given destination.
-
C.
precedingStationOnLine2
Indicates that one station is immediately before another station along the sequence of stops on transit line 2.
-
D.
adjacentStationFormerly
Indicates that two stations were directly adjacent to each other in the past, but are no longer adjacent in the current network configuration.
-
E.
adjacentStationWest
Indicates that one station is immediately to the west of another station in a spatial or network layout.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efb53761b48190954a46e8155a84f0 |
completed | April 27, 2026, 7:12 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:47 p.m.