Triple
T10695586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aérospatiale SA 330J Puma |
E252129
|
entity |
| Predicate | canBeArmed |
P95335
|
FINISHED |
| Object | door-mounted machine guns |
—
|
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: door-mounted machine guns | Statement: [Aérospatiale SA 330J Puma, canBeArmed, door-mounted machine guns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeArmed Context triple: [Aérospatiale SA 330J Puma, canBeArmed, door-mounted machine guns]
-
A.
canBe
Indicates that one entity has the potential, permission, or capability to become, perform as, or be classified as another entity.
-
B.
armedBy
Indicates that one entity is supplied with weapons, equipment, or armaments by another entity.
-
C.
hasArm
Indicates that one entity possesses or is equipped with an arm as a physical part or component of itself.
-
D.
canBeLocked
Indicates that an entity has the capability to be secured or made inaccessible by applying a lock or locking mechanism.
-
E.
hasArms
Indicates that an entity possesses arms as physical appendages.
- F. None of above. chosen
Provenance (4 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_69d6aa5bd7c08190a816e733b4045c23 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fd3af5248190ab807965255e9ad2 |
completed | April 9, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69d6dd8cc0788190b4c02a772e4b58b3 |
completed | April 8, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69d6df47899481909ac0e518d94883cb |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 9:11 p.m.