Triple
T16876889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mekong River Commission |
E421321
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | MRC |
E421321
|
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: MRC | Statement: [Mekong River Commission, shortName, MRC]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MRC Context triple: [Mekong River Commission, shortName, MRC]
-
A.
MRC
MRC is a research and education center at the University of Maryland focused on advancing robotics and autonomous systems.
-
B.
MRC
MRC is an American independent film and television studio known for producing and financing a wide range of acclaimed movies and TV series.
-
C.
MRC
MRC is a major UK organization that funds and supports medical research to improve human health.
-
D.
MRC
chosen
MRC is an intergovernmental organization that coordinates sustainable development and management of the Mekong River basin among its member countries.
-
E.
MCRC
MCRC is the United States Marine Corps Recruiting Command responsible for enlisting and accessing new Marines into the Corps.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3b7f704a081909921d00b3c470472 |
completed | April 18, 2026, 4:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00c2b4abd08190841c5bb0b0eaa177 |
completed | May 10, 2026, 5:39 p.m. |
Created at: April 10, 2026, 5:29 a.m.