Triple
T37378588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .308 Winchester |
E928362
|
entity |
| Predicate | hasCaseCapacityApprox |
P201531
|
FINISHED |
| Object | 56 grains of water |
—
|
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: 56 grains of water | Statement: [.308 Winchester, hasCaseCapacityApprox, 56 grains of water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCaseCapacityApprox Context triple: [.308 Winchester, hasCaseCapacityApprox, 56 grains of water]
-
A.
typicalCapacity
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
B.
storageCapacity
Indicates the maximum amount of data or material that a storage entity can hold.
-
C.
unitCapacity
Indicates the maximum quantity or load that a single unit is designed or allowed to hold, process, or accommodate.
-
D.
canHold
Indicates that one entity has the capacity or ability to contain, support, or carry another entity.
-
E.
canBeHeldIn
Indicates that one entity is capable of being contained, hosted, or conducted within another 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a000014497c819088d5cda3977522dd |
completed | May 10, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69ffff9a52b08190be1024e0fb6fe661 |
completed | May 10, 2026, 3:46 a.m. |
| PDg | Predicate description generation | batch_6a000013004c8190a01710441f881fdc |
completed | May 10, 2026, 3:48 a.m. |
Created at: May 3, 2026, 4:16 p.m.