Triple
T23086336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KMCE |
E575612
|
entity |
| Predicate | hasIATAcode |
P2569
|
FINISHED |
| Object | MCE |
—
|
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: MCE | Statement: [KMCE, hasIATAcode, MCE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MCE Context triple: [KMCE, hasIATAcode, MCE]
-
A.
MCE
chosen
MCE is the three-letter IATA airport code for Merced Regional Airport in Merced, California.
-
B.
MEC
MEC is the commonly used acronym for Uruguay’s Ministry of Education and Culture, the national body responsible for educational policy and cultural affairs.
-
C.
MEC
MEC is the commonly used acronym for the Mountain East Conference, an NCAA Division II collegiate athletic conference in the United States.
-
D.
MEC
MEC is the federal government body responsible for formulating and implementing Brazil’s national education policies and overseeing its education system.
-
E.
MEC
MEC is the reporting mark for the Maine Central Railroad, a historic New England freight and passenger rail carrier.
- 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_69e245bf3e3c819086d3448720efc01b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18da573588190a8e0c859667e64a6 |
completed | April 29, 2026, 4:48 a.m. |
Created at: April 17, 2026, 3:57 p.m.