Triple
T32730124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ariete (licensed derivative) |
E836925
|
entity |
| Predicate | gunModelBasis |
P88584
|
FINISHED |
| Object | Rheinmetall 120 mm smoothbore gun |
—
|
NE NERFINISHED |
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: Rheinmetall 120 mm smoothbore gun | Statement: [Ariete (licensed derivative), gunModelBasis, Rheinmetall 120 mm smoothbore gun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gunModelBasis Context triple: [Ariete (licensed derivative), gunModelBasis, Rheinmetall 120 mm smoothbore gun]
-
A.
mainGunModel
chosen
Indicates the specific model or type designation of the primary gun or main weapon system used by an entity.
-
B.
gunType
Indicates the specific category or kind of gun associated with an entity.
-
C.
gunCalibre
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
-
D.
typeOfGunMount
Indicates the specific kind or configuration of gun mounting used to support or attach a gun.
-
E.
isServiceRifleOf
Indicates that one entity is the designated service rifle used by another entity, typically a military or armed force.
- 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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c8cbb9248190a13b712c81948822 |
completed | May 3, 2026, 4:02 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:11 a.m.