Triple
T15044361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JCR |
E379184
|
entity |
| Predicate | contrastedWith |
P278
|
FINISHED |
| Object | MCR |
unclear NED1
|
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: MCR | Statement: [JCR, contrastedWith, MCR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MCR Context triple: [JCR, contrastedWith, MCR]
-
A.
MCR
MCR is the Middle Common Room, the graduate student community and social/academic body at The Queen’s College, Oxford.
-
B.
MCR
MCR is the Middle Common Room, a graduate student community and social organization typically found at colleges such as St Anne’s College, Oxford.
-
C.
MCR
MCR is the abbreviation commonly used at the University of Cambridge for the Middle Combination Room, the social and representative body for graduate students in a college.
-
D.
MCR
The MCR is the Middle Common Room, a postgraduate student community and social organization within Jesus College.
-
E.
MCR
MCR is the abbreviation for the Midland Counties Railway, a historic 19th-century British railway company that operated in the English Midlands.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide. chosen
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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded830c3c08190a87b81abbbb75377 |
completed | April 15, 2026, 12:13 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe9de54380819084568664b63322d2 |
completed | May 9, 2026, 2:37 a.m. |
Created at: April 10, 2026, 3 a.m.