Triple
T3112150
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type 99 rifle |
E64975
|
entity |
| Predicate | typicalBarrelLength |
P18065
|
FINISHED |
| Object | approximately 660 mm for long rifle |
—
|
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: approximately 660 mm for long rifle | Statement: [Type 99 rifle, typicalBarrelLength, approximately 660 mm for long rifle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBarrelLength Context triple: [Type 99 rifle, typicalBarrelLength, approximately 660 mm for long rifle]
-
A.
typicalLength
chosen
Indicates the usual or characteristic length associated with an entity or phenomenon.
-
B.
hasBarrelConfiguration
Indicates a relationship where an object is characterized by or assigned a specific arrangement or configuration of its barrel or barrels.
-
C.
gunCalibre
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
-
D.
hasLowerBarLength
Indicates that one entity’s bar length is shorter than the bar length of another entity.
-
E.
typicalWeapon
Indicates that the object is a weapon commonly or characteristically used by the subject.
- 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_69ad857eeaf48190b34ebfdaa7a264cf |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada43b0b3c8190a828c9cfcf730ed9 |
completed | March 8, 2026, 4:30 p.m. |
| PD | Predicate disambiguation | batch_69ad9df25d4c81908ff0f6cff55d0563 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.