Triple
T24812168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SA-6 Gainful |
E620818
|
entity |
| Predicate | typicalEngagementCeiling |
P61967
|
FINISHED |
| Object | up to about 14 km |
—
|
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: up to about 14 km | Statement: [SA-6 Gainful, typicalEngagementCeiling, up to about 14 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEngagementCeiling Context triple: [SA-6 Gainful, typicalEngagementCeiling, up to about 14 km]
-
A.
engagementRange
chosen
Indicates the distance or span within which an entity can effectively engage, interact with, or affect another entity.
-
B.
engagementLevel
Indicates the degree or intensity of involvement, interest, or participation one entity has in relation to another entity, activity, or context.
-
C.
engagementOf
Indicates a relationship where an engagement, commitment, or formal involvement is associated with or attributed to a specific entity.
-
D.
typicalParticipation
Indicates that an entity commonly or characteristically takes part in a particular activity, event, or process.
-
E.
engagementScale
Indicates the degree or intensity of involvement, interest, or participation in an activity, interaction, or relationship.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 18, 2026, 4:50 a.m.