Triple
T8865943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IMO convention |
E211018
|
entity |
| Predicate | adoptedBy |
P1034
|
FINISHED |
| Object | IMO |
E5843
|
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: IMO | Statement: [IMO convention, adoptedBy, IMO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IMO Context triple: [IMO convention, adoptedBy, IMO]
-
A.
IMO
chosen
IMO is a specialized United Nations agency responsible for regulating international shipping and promoting maritime safety, security, and environmental protection.
-
B.
International Mathematical Olympiad
The International Mathematical Olympiad is the world’s premier annual mathematics competition for high school students, renowned for its extremely challenging problems and for identifying future leading mathematicians.
-
C.
JMO
JMO is the IATA airport code for Jomsom Airport, a domestic airport serving the town of Jomsom in Nepal’s Mustang region.
-
D.
MOP
MOP is the ISO 4217 currency code for the Macanese pataca, the official currency of Macau.
-
E.
JBMOU
JBMOU is a NATO standardization agreement that harmonizes ballistic data and procedures among member nations to ensure interoperability of artillery and related weapon systems.
- 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_69ca838d3c7c8190a849566d5afd2b11 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6106d41081909db710bda8aaf6fd |
completed | April 1, 2026, 12:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfa0d311148190823cc047e2908bc0 |
completed | April 3, 2026, 11:13 a.m. |
Created at: March 30, 2026, 6:51 p.m.