Triple
T16522179
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SEDI |
E401346
|
entity |
| Predicate | acronym |
P43
|
FINISHED |
| Object | SEDI |
E401346
|
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: SEDI | Statement: [SEDI, acronym, SEDI]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SEDI Context triple: [SEDI, acronym, SEDI]
-
A.
SEDI
chosen
SEDI is the Executive Secretariat for Integral Development, a specialized body of the Organization of American States that promotes inclusive and sustainable development across member countries.
-
B.
SE-D
SE-D is the ISO 3166-2 regional code assigned to Dalarna County in Sweden.
-
C.
SED
SED was the ruling Marxist–Leninist party that governed East Germany (the German Democratic Republic) from its founding in 1949 until the end of communist rule in 1989.
-
D.
SED
SED is the CTA station code for the Sedgwick station on Chicago’s 'L' rapid transit system.
-
E.
SEDEF
SEDEF is the Spanish Ministry of Defence’s Secretariat of State responsible for high-level planning, management, and administration of national defense policy and resources.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e8158cc8190aa77c6d37bd7ec76 |
completed | April 18, 2026, 7:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a006088fe4881909e5b691743157700 |
completed | May 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 5:14 a.m.