Triple
T35144142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 7.7×58mm Arisaka |
E1014773
|
entity |
| Predicate | relatedCartridge |
P9007
|
FINISHED |
| Object | .303 British |
E713953
|
NE 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: .303 British | Statement: [7.7×58mm Arisaka, relatedCartridge, .303 British]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedCartridge Context triple: [7.7×58mm Arisaka, relatedCartridge, .303 British]
-
A.
requiresCartridgeSlotOf
Indicates that one entity needs to use or be connected to the cartridge slot provided by another entity in order to function or be compatible.
-
B.
cartridge
chosen
Indicates that one entity is a cartridge associated with, contained in, or used by another entity.
-
C.
alsoCarries
Indicates that an entity, in addition to other items or responsibilities it has, carries another specified item or load as well.
-
D.
intendedCartridgeStandard
Indicates that an item is designed to be used with, or conform to, a particular cartridge standard.
-
E.
hasCartridgeSlot
Indicates that an object includes a dedicated slot or receptacle designed to accept and hold a cartridge.
- F. None of above.
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_69f76dda7c108190a2ffd93eb6c341a7 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37d95c5c388190b1b81a66274cf49e |
completed | June 21, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:02 p.m.