Triple
T21268773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Morges railway station |
E524199
|
entity |
| Predicate | hasStationCode |
P1289
|
FINISHED |
| Object | MOR |
—
|
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: MOR | Statement: [Morges railway station, hasStationCode, MOR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MOR Context triple: [Morges railway station, hasStationCode, MOR]
-
A.
MOR
MOR is the IATA airport code for Morristown Regional Airport in Tennessee, United States.
-
B.
MOR
MOR is the ICAO airline designator assigned to the former U.S. low-fare carrier Morris Air.
-
C.
MOR
chosen
MOR is the station code for Morges railway station, a key rail stop in the town of Morges in the canton of Vaud, Switzerland.
-
D.
MOR
MOR is the station code for Mo i Rana Station, a railway station in the town of Mo i Rana in Nordland county, Norway.
-
E.
MOR
MOR is the former Ministry of Railways of the People’s Republic of China, the government body that once oversaw the country’s railway planning, construction, and operations.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73651115081908b5083ba818a6bb1 |
completed | April 21, 2026, 8:33 a.m. |
Created at: April 16, 2026, 4:01 p.m.