Triple
T22439111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .38 Special |
E554705
|
entity |
| Predicate | neckDiameter |
P148196
|
FINISHED |
| Object | 0.379 inch |
—
|
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: 0.379 inch | Statement: [.38 Special, neckDiameter, 0.379 inch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neckDiameter Context triple: [.38 Special, neckDiameter, 0.379 inch]
-
A.
bodyDiameter
Indicates the measurement of how wide an object's body is across its broadest cross-section.
-
B.
neckCharacteristic
Indicates that an entity has a specific attribute, feature, or quality related to its neck.
-
C.
shellDiameter
Indicates the diameter measurement of a shell, typically specifying the distance across it at its widest point.
-
D.
leadDiameter
Indicates the diameter measurement of a lead (such as a wire, pin, or conductive element) in a component or structure.
-
E.
hasShoulderDiameter
Indicates the diameter measurement of an entity’s shoulder region or shoulder-related feature.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae01bd08190aee5141f4c0848bc |
completed | April 29, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa39e3388190b659d59948ebf3e6 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:47 p.m.