Triple
T29724199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RB199-34R Mk 101 |
E752134
|
entity |
| Predicate | primaryMissionSupport |
P98783
|
FINISHED |
| Object | strike missions |
—
|
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: strike missions | Statement: [RB199-34R Mk 101, primaryMissionSupport, strike missions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMissionSupport Context triple: [RB199-34R Mk 101, primaryMissionSupport, strike missions]
-
A.
typeOfMissionSupport
chosen
Indicates the kind or category of support provided in relation to a specific mission.
-
B.
primaryMissionTo
Indicates that an entity has a main or principal mission directed toward or focused on another entity.
-
C.
primaryMissionDependency
Indicates that one mission’s success, initiation, or continuation depends directly on the completion or outcome of another mission.
-
D.
primaryMissionProgram
Indicates that an entity serves as the main or principal program under which another entity’s mission or primary activity is organized or executed.
-
E.
primaryMissions
Indicates the main missions or core objectives assigned to or undertaken by an entity.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a017a360f088190acd5933aa353e763 |
completed | May 11, 2026, 6:41 a.m. |
| PD | Predicate disambiguation | batch_6a0179d3f78c8190b1d2e8829619fa54 |
completed | May 11, 2026, 6:40 a.m. |
Created at: April 28, 2026, 7:38 p.m.