Triple
T25218983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 9M317 |
E631907
|
entity |
| Predicate | targetEngagementEnvironment |
P70999
|
FINISHED |
| Object | low to medium 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: low to medium altitude | Statement: [9M317, targetEngagementEnvironment, low to medium altitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetEngagementEnvironment Context triple: [9M317, targetEngagementEnvironment, low to medium altitude]
-
A.
engagementEnvironment
chosen
Indicates the situational context or setting in which an interaction, activity, or engagement takes place.
-
B.
hasEnvironmentalTarget
Indicates that an entity has a specified environmental objective, goal, or target it aims to achieve or comply with.
-
C.
targetedActivity
Indicates that an activity is specifically directed or focused toward a particular entity, group, or objective.
-
D.
targetArea
Indicates the specific area or region that is the intended focus or destination of an action or effect.
-
E.
targetsEcosystem
Indicates that an action, product, or policy is directed toward, affects, or is specifically intended for a particular ecosystem.
- 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 21, 2026, 12:59 p.m.