Triple
T7232117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Preparedness Goal |
E154926
|
entity |
| Predicate | organizesCapabilitiesAcross |
P56209
|
FINISHED |
| Object | prevention mission area |
—
|
LITERAL 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: prevention mission area | Statement: [National Preparedness Goal, organizesCapabilitiesAcross, prevention mission area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizesCapabilitiesAcross Context triple: [National Preparedness Goal, organizesCapabilitiesAcross, prevention mission area]
-
A.
plannedCapability
Indicates that an entity is intended or scheduled to possess or provide a particular capability in the future.
-
B.
providesCapabilityTo
Indicates that one entity enables or equips another entity with a specific capability or functionality.
-
C.
associatedCapability
chosen
Indicates that one entity has a related ability, function, or competence that is linked to or relevant for another entity.
-
D.
organizesInto
Indicates that one entity arranges, structures, or groups another entity into a particular order, system, or set of categories.
-
E.
deploymentCapability
Indicates the ability or capacity of an entity to deploy, release, or roll out another entity (such as a system, service, or resource) into an operational environment.
- F. None of above.
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_69c68811dd1c8190ac460bb39e64e1f0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea552a688190a00f5d0ad982f787 |
completed | March 27, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69c6e7644648819096a5e2de5d0dbe97 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.