Triple
T1798268
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centauro tank destroyer |
E39653
|
entity |
| Predicate | gunStabilization |
P6077
|
FINISHED |
| Object | stabilized main gun |
—
|
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: stabilized main gun | Statement: [Centauro tank destroyer, gunStabilization, stabilized main gun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gunStabilization Context triple: [Centauro tank destroyer, gunStabilization, stabilized main gun]
-
A.
gunStabilisation
chosen
Indicates that an entity performs or provides stabilization for a gun, reducing its movement or recoil to improve accuracy.
-
B.
fireControlSystem
Indicates a relationship where a system monitors, directs, and coordinates the detection, targeting, and firing of weapons or other actuators to control the application of force or energy.
-
C.
gunType
Indicates the specific category or kind of gun associated with an entity.
-
D.
gunCalibre
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
-
E.
gun
Indicates that one entity uses, carries, or is associated with a gun in relation to another entity or context.
- 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_69a88632aa588190ba3978fde0db5bbd |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab61b6ea188190aab9fb839bf1e367 |
completed | March 6, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69aa61d2f7a8819090301f92d3e358c7 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:32 p.m.