Triple
T36981845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MDW |
E914849
|
entity |
| Predicate | hasAdjacentStationCode |
P181057
|
FINISHED |
| Object | MAI |
—
|
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: MAI | Statement: [MDW, hasAdjacentStationCode, MAI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdjacentStationCode Context triple: [MDW, hasAdjacentStationCode, MAI]
-
A.
hasAdjacentStationOnG
Indicates that one station is directly next to another station along line G in the network.
-
B.
hasAdjacentStationOnM
Indicates that one station is directly next to another station along metro line M, with no other stations in between.
-
C.
hasAdjacentStationOnE
Indicates that one station is directly adjacent to another station on the east side.
-
D.
hasAdjacentStationOnAC
Indicates that one station is directly next to another station along the AC line or route.
-
E.
hasAdjacentStations
chosen
Indicates that two stations are directly next to each other in a sequence or network, with no other station in between.
- 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_69f76e8dd0408190b8b46da118ea5128 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: May 3, 2026, 4:14 p.m.