Triple
T838930
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North American Aerospace Defense Command |
E18132
|
entity |
| Predicate | typeOfWarning |
P1950
|
FINISHED |
| Object | aerospace warning |
—
|
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: aerospace warning | Statement: [North American Aerospace Defense Command, typeOfWarning, aerospace warning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfWarning Context triple: [North American Aerospace Defense Command, typeOfWarning, aerospace warning]
-
A.
warnsAbout
Indicates that one entity alerts or cautions another entity about a potential danger, risk, or problem.
-
B.
typeOfFaulting
Indicates the kind or classification of geological faulting that characterizes the relationship between rock units or structures.
-
C.
hazardType
chosen
Indicates the specific kind or category of hazard associated with an entity or situation.
-
D.
issueType
Indicates the specific category or classification assigned to an issue within a tracking or management context.
-
E.
guidanceType
Indicates the specific kind or category of guidance being provided or referenced in the relationship between entities.
- 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_69a49389f44881909a608fb27d89f247 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4abe4ab1081909207ae2eec1898d9 |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7dfc5c8190890c9df485d73a86 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.