Triple
T2456077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | James McCudden |
E54423
|
entity |
| Predicate | hasHonorificTitle |
P368
|
FINISHED |
| Object | MC |
E25585
|
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: MC | Statement: [James McCudden, hasHonorificTitle, MC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MC Context triple: [James McCudden, hasHonorificTitle, MC]
-
A.
MC
MC is the official abbreviation for NATO’s highest military authority, the NATO Military Committee.
-
B.
MC
chosen
MC is the postnominal abbreviation used to denote recipients of the Military Cross, a British military decoration awarded for gallantry during active operations against the enemy.
-
C.
Mc
Mc is a Gaelic patronymic prefix meaning "son of," commonly found in Scottish and Irish surnames.
-
D.
.mc
.mc is the country code top-level domain (ccTLD) assigned to the Principality of Monaco for use in its internet addresses.
-
E.
CM
CM is the post-nominal letters used to denote a Member of the Order of Canada, one of the country’s highest civilian honors.
- 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_69ab49dee84c819096b50a0049c347ac |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd105054c819081286729749a347c |
completed | March 7, 2026, 7:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69aef0ca655c81908612983ced5f5786 |
completed | March 9, 2026, 4:09 p.m. |
Created at: March 6, 2026, 9:44 p.m.