Triple
T2363708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Council of Europe |
E47331
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | CoE |
E47331
|
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: CoE | Statement: [Council of Europe, shortName, CoE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CoE Context triple: [Council of Europe, shortName, CoE]
-
A.
CoE
chosen
CoE is the commonly used abbreviation for the Council of Europe, a pan-European intergovernmental organization focused on promoting human rights, democracy, and the rule of law.
-
B.
SCoE
SCoE is the U.S. Army’s Sustainment Center of Excellence, responsible for developing doctrine, training, and capabilities for logistics and sustainment operations.
-
C.
MCoE
MCoE is the U.S. Army’s primary training and doctrine center for maneuver forces, integrating infantry, armor, and related capabilities at Fort Moore, Georgia.
-
D.
CoR
CoR is the commonly used abbreviation for the European Committee of the Regions, the EU’s advisory body representing local and regional authorities.
-
E.
MCCoE
MCCoE is a U.S. Army organization responsible for developing and integrating mission command doctrine, concepts, and training across the force.
- 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc746e7048190a09a38401b367628 |
completed | March 7, 2026, 6:35 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69aeb3c5c4b881909ad3223206fb2940 |
completed | March 9, 2026, 11:49 a.m. |
Created at: March 4, 2026, 7:55 p.m.