Triple
T14773150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maine Mariners |
E347185
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | MNE |
E24858
|
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: MNE | Statement: [Maine Mariners, abbreviation, MNE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MNE Context triple: [Maine Mariners, abbreviation, MNE]
-
A.
MNE
MNE is the three-letter ISO 3166-1 alpha-3 country code assigned to Montenegro.
-
B.
MNE
MNE is the commonly used acronym for Portugal’s Ministry of Foreign Affairs, the government body responsible for the country’s diplomatic relations and foreign policy.
-
C.
MNE
chosen
MNE is the standard abbreviation used for the Maine Celtics, an NBA G League basketball team based in Portland, Maine.
-
D.
MNI
MNI is the IATA airport code for John A. Osborne Airport on the Caribbean island of Montserrat.
-
E.
MNI
MNI is the official abbreviation used in India to denote a Monument of National Importance, a protected heritage site recognized for its historical and cultural significance.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec81485e08190be35baafcf22b6f2 |
completed | April 14, 2026, 11:04 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe0cfd26fc81909fba39c8705437ed |
completed | May 8, 2026, 4:19 p.m. |
Created at: April 10, 2026, 1:31 a.m.