Triple
T8049248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NDHQ |
E187632
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | NDHQ |
E187632
|
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: NDHQ | Statement: [NDHQ, abbreviation, NDHQ]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: NDHQ Context triple: [NDHQ, abbreviation, NDHQ]
-
A.
NDHQ
chosen
NDHQ is the central administrative and command headquarters of the Canadian Armed Forces and the Department of National Defence.
-
B.
NSHQ
NSHQ is NATO’s central command responsible for coordinating and overseeing special operations forces across the Alliance.
-
C.
NDH
NDH was the fascist puppet state established by the Axis powers in World War II on the territory of occupied Croatia and Bosnia and Herzegovina.
-
D.
DNH
DNH is the abbreviated name for the Department of National Heritage, a government body responsible for preserving and promoting a nation's cultural and historical assets.
-
E.
DHN
DHN is the IATA airport code for Dothan Regional Airport serving the Dothan, Alabama area in the United States.
- 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_69ca82b15e948190a62fd7af5218426a |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3f7826288190b2f292a7d34fcd80 |
completed | March 31, 2026, 3:28 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cc5716934481908ec60cc9fd825ad7 |
completed | March 31, 2026, 11:21 p.m. |
Created at: March 30, 2026, 5:24 p.m.