Triple
T17750085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GAU-8 Avenger |
E443088
|
entity |
| Predicate | recoilForce |
P123534
|
FINISHED |
| Object | very high recoil |
—
|
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: very high recoil | Statement: [GAU-8 Avenger, recoilForce, very high recoil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recoilForce Context triple: [GAU-8 Avenger, recoilForce, very high recoil]
-
A.
recoilLevel
chosen
Indicates the degree or intensity of backward force or kick produced when an action (such as firing a weapon or operating a device) occurs.
-
B.
recoveryForce
Indicates the force exerted to restore an object or system from a displaced, deformed, or disturbed state back toward its original or equilibrium condition.
-
C.
forceDirection
Indicates the direction in which a force is applied or exerted in the relationship between entities.
-
D.
axisForce
Indicates a force applied along a specific axis or direction between entities.
-
E.
associatedForce
Indicates that there is a force linked or connected to an entity, typically representing the physical influence acting on or exerted by that 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48418c0188190beb31809b40e4648 |
completed | April 19, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:10 a.m.