Triple
T4077585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO Nuclear Planning Group |
E87401
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | NPG |
E87401
|
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: NPG | Statement: [NATO Nuclear Planning Group, shortName, NPG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NPG Context triple: [NATO Nuclear Planning Group, shortName, NPG]
-
A.
NPG
chosen
NPG is the commonly used abbreviation for NATO’s Nuclear Planning Group, the alliance’s senior body for nuclear policy and planning.
-
B.
.np
.np is the country code top-level domain (ccTLD) assigned to Nepal for use in internet addresses.
-
C.
NVP
NVP is the official station code for Nieuw-Vennep railway station in the Netherlands.
-
D.
NPA
NPA is the central national law enforcement body of Japan responsible for overseeing police operations and public security across the country.
-
E.
NAP
NAP is the publishing arm of the U.S. National Academies that produces and disseminates authoritative reports on science, engineering, and medicine.
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc4d348c8190a94724639830aca0 |
completed | March 9, 2026, 4:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69b562bea9b48190bcd1396c0cb19697 |
completed | March 14, 2026, 1:29 p.m. |
Created at: March 9, 2026, 3:39 p.m.