Triple
T30172202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NATO member defence ministries |
E766949
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government organization collection |
C23808
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: government organization collection Context triple: [NATO member defence ministries, instanceOf, government organization collection]
-
A.
government document collection
A government document collection is an organized set of official records, reports, laws, and publications produced or issued by governmental bodies, maintained for reference, accountability, and public access.
-
B.
administrative body collection
chosen
An administrative body collection is an organized grouping of official entities or agencies responsible for managing, regulating, or overseeing specific governmental or institutional functions.
-
C.
governmental organization
A governmental organization is a formally structured public entity established by a government to create, implement, or enforce laws, policies, and services for a specific jurisdiction or public purpose.
-
D.
intergovernmental organization records
Intergovernmental organization records are documented materials produced, received, or maintained by organizations formed by sovereign states to facilitate cooperation, coordination, and decision-making on international or regional issues.
-
E.
government information center
A government information center is a public facility or service that provides citizens with access to official information, resources, and assistance regarding government programs, services, and regulations.
- F. None of above.
Provenance (1 batch)
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_69f2247ba20c81909d34f2bfed706e1e |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:24 p.m.