Triple
T28309195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .223 Remington |
E713949
|
entity |
| Predicate | standardTwistRateCommon |
P129461
|
FINISHED |
| Object | 1:9 inches |
—
|
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: 1:9 inches | Statement: [.223 Remington, standardTwistRateCommon, 1:9 inches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardTwistRateCommon Context triple: [.223 Remington, standardTwistRateCommon, 1:9 inches]
-
A.
twistType
Indicates the specific manner or category of twisting applied in a relationship or action between entities.
-
B.
twistCount
Indicates the number of twists or rotational turns applied or present in the relationship between the related entities.
-
C.
hasTwist
Indicates that an entity (such as a story, object, or feature) includes an unexpected change, reversal, or surprising element relative to what was previously established or anticipated.
-
D.
typicalRate
chosen
Indicates the standard or commonly expected rate at which something occurs, is charged, or is applied in a given context.
-
E.
standardPar
Indicates that two entities are parallel and conform to a recognized or defined standard of parallelism.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 27, 2026, 11:39 p.m.