Triple
T7577940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MRIA |
E179405
|
entity |
| Predicate | postNominalLetters |
P1600
|
FINISHED |
| Object | MRIA |
E179405
|
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: MRIA | Statement: [MRIA, postNominalLetters, MRIA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MRIA Context triple: [MRIA, postNominalLetters, MRIA]
-
A.
MRIA
MRIA is the abbreviation for Mattala Rajapaksa International Airport, a major international airport located in southern Sri Lanka.
-
B.
MRIA
chosen
MRIA is the post-nominal title indicating membership of the Royal Irish Academy, an all-Ireland body of distinguished scholars and scientists.
-
C.
MRA
MRA is the IATA airport code for Misrata International Airport, a commercial airport serving the city of Misrata in Libya.
-
D.
MRI
MRI (Matz's Ruby Interpreter) is the standard reference implementation of the Ruby programming language, written in C and known for prioritizing simplicity and developer happiness.
-
E.
MNI
MNI is the IATA airport code for John A. Osborne Airport on the Caribbean island of Montserrat.
- 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_69c69f327db881909a21ae3b156f8ded |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f94cdbec81909f2ba7ce04e49931 |
completed | March 27, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c8616d87f881909fe23220dc77167c |
completed | March 28, 2026, 11:17 p.m. |
Created at: March 27, 2026, 3:51 p.m.