Triple
T31990017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 152 mm ShKH vz. 77 DANA |
E816837
|
entity |
| Predicate | upgradePotential |
P25630
|
FINISHED |
| Object | modern digital fire-control systems |
—
|
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: modern digital fire-control systems | Statement: [152 mm ShKH vz. 77 DANA, upgradePotential, modern digital fire-control systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: upgradePotential Context triple: [152 mm ShKH vz. 77 DANA, upgradePotential, modern digital fire-control systems]
-
A.
upgradeType
Indicates the specific kind or category of improvement or enhancement applied to an entity relative to its previous state.
-
B.
upgradeOption
Indicates that one entity serves as a possible improved or higher-level alternative to another entity.
-
C.
upgradeEligibility
Indicates whether an entity qualifies to move from its current version, level, or plan to a higher or more advanced one under defined criteria.
-
D.
upgradeOf
Indicates that one entity is a newer, improved, or more advanced version of another entity.
-
E.
upgradeTechnology
chosen
Indicates improving or replacing existing technology with a more advanced, efficient, or capable version.
- 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_69f348f8002081909a3588758ba94afb |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b3b8e360819095a9882acb3e3d21 |
completed | May 3, 2026, 2:32 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:13 a.m.