Triple
T2618823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | THAAD batteries |
E58954
|
entity |
| Predicate | engagementAltitudeCategory |
P35392
|
FINISHED |
| Object | high-altitude |
—
|
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: high-altitude | Statement: [THAAD batteries, engagementAltitudeCategory, high-altitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engagementAltitudeCategory Context triple: [THAAD batteries, engagementAltitudeCategory, high-altitude]
-
A.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
B.
altitudeCategory
chosen
Indicates the classification of something based on its height or elevation relative to a reference level (e.g., low, medium, high altitude).
-
C.
altitudeCapability
Indicates the maximum or typical altitude at which an entity can effectively operate or function.
-
D.
elevationType
Indicates the kind or classification of elevation associated with an entity, such as how its height or altitude is characterized.
-
E.
engagementLevel
Indicates the degree or intensity of involvement, interest, or participation one entity has in relation to another entity, activity, or context.
- 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_69ab4ac444dc819099614e534dd6021f |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdaca581881908fe8d3d820f839b7 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd80f48888190afdf7e3e042157d0 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:50 p.m.