Triple
T14046974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MAS |
E337980
|
entity |
| Predicate | hasNearbyStationCode |
P77644
|
FINISHED |
| Object | MS |
—
|
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: MS | Statement: [MAS, hasNearbyStationCode, MS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyStationCode Context triple: [MAS, hasNearbyStationCode, MS]
-
A.
hasStationNear
chosen
Indicates that one entity has a station located in close proximity to another entity.
-
B.
hasAdjacentStationOnAC
Indicates that one station is directly next to another station along the AC line or route.
-
C.
hasStationCode
Indicates that an entity is associated with a specific station identification code.
-
D.
hasAdjacentStationOnIND
Indicates that one station is directly next to another station on the IND (Independent Subway System) line, with no other stations in between.
-
E.
hasNearbyInterchange
Indicates that one location has a transportation interchange (such as a junction or transfer point) situated close 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_69d81c664e48819088cbd8f433aeffe5 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de312df37081909f45ce3e219af5dc |
completed | April 14, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.