Triple
T6784288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fulcrum |
E155760
|
entity |
| Predicate | associatedWithWeaponSystems |
P67648
|
FINISHED |
| Object | air-to-air missiles |
—
|
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: air-to-air missiles | Statement: [Fulcrum, associatedWithWeaponSystems, air-to-air missiles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithWeaponSystems Context triple: [Fulcrum, associatedWithWeaponSystems, air-to-air missiles]
-
A.
associatedWithWeapon
Indicates that an entity has a connection or involvement with a weapon, such as ownership, use, presence, or relevance in a given context.
-
B.
associatedWithMissile
Indicates a relationship in which an entity is connected or linked to a missile, such as through ownership, use, design, deployment, or operational involvement.
-
C.
relatedToWeaponType
chosen
Indicates that an entity has an association or connection with a specific type or category of weapon.
-
D.
introducedWeaponSystem
Indicates that an entity caused a new weapon system to be brought into use or formally adopted.
-
E.
usesMissileSystem
Indicates that one entity employs or operates a particular missile system as part of its capabilities or actions.
- 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d28bdc3c8190aa60616d89db66ed |
completed | March 27, 2026, 6:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d095dcac8190bb9b943f50a7f885 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:14 p.m.