Triple
T19306249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beretta AR70/90 |
E482835
|
entity |
| Predicate | ejection |
P135203
|
FINISHED |
| Object | right-side ejection |
—
|
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: right-side ejection | Statement: [Beretta AR70/90, ejection, right-side ejection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ejection Context triple: [Beretta AR70/90, ejection, right-side ejection]
-
A.
ejectionRecord
Indicates that there is a recorded instance of an entity being expelled, removed, or discharged from a place, system, or context.
-
B.
expel
Indicates forcing an entity to leave or be removed from a place, group, or situation, typically as a punishment or consequence.
-
C.
involvesParticleEjection
Indicates that the action or process includes the emission or release of particles from a source.
-
D.
typicalEjectedMass
Indicates the characteristic amount of mass that is usually expelled from a system or object during an ejection event.
-
E.
emitted
Indicates that one entity has released, discharged, or sent out another entity, such as energy, particles, signals, or substances, into its surroundings.
- 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e604c84fe08190869463bdd0324160 |
completed | April 20, 2026, 10:49 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4ddcf50108190a09d0f1291c17374 |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 1:31 p.m.