Triple
T31989510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | vz. 58 rifle |
E816824
|
entity |
| Predicate | fieldStripping |
P106330
|
FINISHED |
| Object | top cover hinged forward |
—
|
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: top cover hinged forward | Statement: [vz. 58 rifle, fieldStripping, top cover hinged forward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldStripping Context triple: [vz. 58 rifle, fieldStripping, top cover hinged forward]
-
A.
fieldComposition
Indicates how the components or elements within a field are organized, combined, or structured in relation to one another.
-
B.
fieldStrategy
Indicates a strategic approach or plan applied within a particular field, domain, or area of activity.
-
C.
fieldPattern
Indicates a recurring or structured arrangement or configuration present within a field or area.
-
D.
fieldNormalization
Indicates that a field’s values are being transformed or scaled into a standardized form to enable consistent comparison or processing across different records or datasets.
-
E.
canBeStrippedFor
chosen
Indicates that one entity is capable of having parts or layers removed in order to benefit, prepare, or expose another 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 12:13 a.m.