Triple
T958685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxford Road railway station |
E20683
|
entity |
| Predicate | stationCode |
P1289
|
FINISHED |
| Object | MCO |
E20683
|
NE 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: MCO | Statement: [Oxford Road railway station, stationCode, MCO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MCO Context triple: [Oxford Road railway station, stationCode, MCO]
-
A.
MCO
chosen
MCO is the National Rail station code used to identify Oxford Road railway station in Manchester, England.
-
B.
MCO
MCO is the three-letter ISO 3166-1 alpha-3 country code assigned to the Principality of Monaco.
-
C.
MCRC
MCRC is the United States Marine Corps Recruiting Command responsible for enlisting and accessing new Marines into the Corps.
-
D.
MCA
MCA was a major American record label and entertainment company known for signing prominent artists and producing a wide range of popular music releases.
-
E.
NMOC
NMOC is an abbreviation commonly used for a Network Manager Operations Centre, a facility responsible for overseeing and coordinating network operations and performance.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a493b21f2881908132dcf45dcd2f36 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b3fc94ec8190b55c6cdf3a37d6b5 |
completed | March 1, 2026, 9:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ac11a212f08190ae2aad947226d09c |
completed | March 7, 2026, 11:53 a.m. |
Created at: March 1, 2026, 7:40 p.m.