Triple
T19843604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beretta 686 |
E476799
|
entity |
| Predicate | ejectorType |
P137551
|
FINISHED |
| Object | automatic ejectors |
—
|
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: automatic ejectors | Statement: [Beretta 686, ejectorType, automatic ejectors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ejectorType Context triple: [Beretta 686, ejectorType, automatic ejectors]
-
A.
ejection
Indicates the forceful expulsion or removal of one entity from another entity, system, or location.
-
B.
nozzleType
Indicates the specific kind or category of nozzle associated with or used by an entity.
-
C.
hasEjectionSeat
Indicates that an object (typically a vehicle or cockpit) is equipped with an ejection seat that allows an occupant to be forcibly expelled for emergency escape.
-
D.
hasEjecta
Indicates that one entity produces or is associated with material expelled or thrown out from another entity as a result of an energetic event or process.
-
E.
exhaustType
Indicates the specific kind or configuration of exhaust system associated with an entity.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65806ea888190850421154238d91c |
completed | April 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:51 p.m.