Triple
T31815922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TAM VCA 155 |
E812131
|
entity |
| Predicate | caliberClass |
P172928
|
FINISHED |
| Object | heavy artillery |
—
|
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: heavy artillery | Statement: [TAM VCA 155, caliberClass, heavy artillery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caliberClass Context triple: [TAM VCA 155, caliberClass, heavy artillery]
-
A.
natoCaliberClass
Indicates that two ammunition types share the same standardized NATO caliber classification.
-
B.
gunCalibre
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
-
C.
notableCaliber
Indicates that an entity is recognized for having a particularly significant, distinguished, or high level of quality, ability, or importance.
-
D.
supportsCaliber
Indicates that one entity is compatible with and able to accommodate or function with a specified caliber.
-
E.
barrelLengthInCalibers
Indicates the length of a barrel expressed as a multiple of its bore diameter (in calibers), describing how many times the bore diameter fits into the barrel length.
- 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_69f348e846c081908eb468a0665afd55 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b0d21dd08190a9883ff71c94c71c |
completed | May 3, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6afeaaef88190aefa97e83f8db906 |
completed | May 3, 2026, 2:16 a.m. |
Created at: April 30, 2026, 11:44 p.m.