Triple
T649707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mauser BK-27 |
E11318
|
entity |
| Predicate | barrelConfiguration |
P2093
|
FINISHED |
| Object | single-barrel |
—
|
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: single-barrel | Statement: [Mauser BK-27, barrelConfiguration, single-barrel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: barrelConfiguration Context triple: [Mauser BK-27, barrelConfiguration, single-barrel]
-
A.
barAdmission
Indicates that a legal professional has been formally admitted to practice law before a particular bar or court.
-
B.
bowlAccess
Indicates that one entity has the ability or permission to access or use a particular bowl.
-
C.
configuration
chosen
Indicates that one entity specifies or defines the arrangement, setup, or parameter settings under which another entity operates or is structured.
-
D.
shellType
Indicates the type or classification of a shell associated with an entity (e.g., its form, structure, or category).
-
E.
tailConfiguration
Indicates how the tail of an entity is arranged, structured, or positioned relative to the rest of 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f31e70c81909a2ac1d939f7ec07 |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0eade081909c47e85ed55f808d |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.