Triple
T28073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Oceanic and Atmospheric Administration |
E561
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | meteorological organization |
C656
|
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: meteorological organization Context triple: [National Oceanic and Atmospheric Administration, instanceOf, meteorological organization]
-
A.
military organization
A military organization is a structured group of armed forces personnel and resources, organized under a defined hierarchy and command system, to plan, coordinate, and conduct defense and combat operations in support of a state’s strategic objectives.
-
B.
international organization
An international organization is an institutional entity formed by multiple countries or global actors to coordinate policies, manage shared interests, and address transnational issues through cooperative frameworks and agreements.
-
C.
medical organization
A medical organization is an entity that coordinates healthcare services, resources, and professionals to promote, maintain, or restore people’s health.
-
D.
intergovernmental organization
An intergovernmental organization is a formal entity created by sovereign states through treaties or agreements to cooperate on common interests, coordinate policies, and address international issues.
-
E.
military communications organization
A military communications organization is a structured unit responsible for planning, managing, and operating secure, reliable information and communication systems that support command, control, and coordination of military forces.
- F. None of above. chosen
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_69a2479dec388190967ba648663442c9 |
completed | Feb. 28, 2026, 1:40 a.m. |
Created at: Feb. 28, 2026, 1:44 a.m.