Triple
T37378585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .308 Winchester |
E928362
|
entity |
| Predicate | commercialEquivalentOf |
P58587
|
FINISHED |
| Object | 7.62×51mm NATO |
—
|
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: 7.62×51mm NATO | Statement: [.308 Winchester, commercialEquivalentOf, 7.62×51mm NATO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commercialEquivalentOf Context triple: [.308 Winchester, commercialEquivalentOf, 7.62×51mm NATO]
-
A.
equivalentIn
chosen
Indicates that two entities are considered logically or functionally the same in meaning, status, or effect within a given context.
-
B.
commercialProduct
Indicates that one entity is a product or service offered for sale or commercial use by another entity.
-
C.
concurrentProductWith
Indicates that two or more products are available, used, or occur at the same time within the same context or transaction.
-
D.
commercializedIn
Indicates that something has been brought to market or made available for commercial sale or use within a specified place or context.
-
E.
commercialAvailability
Indicates that an entity is offered for sale or otherwise obtainable through commercial channels.
- 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:16 p.m.