Triple
T8327939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNMIL |
E195000
|
entity |
| Predicate | predecessor |
P97
|
FINISHED |
| Object | ECOMIL |
E195001
|
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: ECOMIL | Statement: [UNMIL, predecessor, ECOMIL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ECOMIL Context triple: [UNMIL, predecessor, ECOMIL]
-
A.
ECOMIL
chosen
ECOMIL was a West African regional peacekeeping force deployed to stabilize Liberia and support the end of the Second Liberian Civil War.
-
B.
Enneco
Enneco is a medieval Basque given name, historically associated with early Navarrese nobility and considered an antecedent of the name Íñigo.
-
C.
EKO
EKO is the three-letter IATA airport code for Elko Regional Airport, a public airport serving Elko, Nevada, in the United States.
-
D.
EKM
EKM is a Protestant regional church body in Germany that forms part of the Evangelical Church in Germany (EKD).
-
E.
Ecolo
Ecolo is a Belgian French- and German-speaking green political party known for its focus on environmentalism, social justice, and progressive policies.
- 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_69ca82e87f2c8190bdb71ee29dfc642d |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7f8243288190b1ae74d69395fc91 |
completed | March 31, 2026, 8:02 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd95b92708819097795498f9ebcdfc |
completed | April 1, 2026, 10:01 p.m. |
Created at: March 30, 2026, 5:56 p.m.