Triple
T31798762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SK-105A3 |
E811668
|
entity |
| Predicate | hasUpgradeFeature |
P5357
|
FINISHED |
| Object | modernized fire control system |
—
|
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: modernized fire control system | Statement: [SK-105A3, hasUpgradeFeature, modernized fire control system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUpgradeFeature Context triple: [SK-105A3, hasUpgradeFeature, modernized fire control system]
-
A.
hasUpgrade
chosen
Indicates that one entity possesses, includes, or is associated with an improved or enhanced version of another entity.
-
B.
hasUpgradeSystem
Indicates that an entity includes or is equipped with a system for performing upgrades or enhancements.
-
C.
hasUpgradeProject
Indicates that an entity is associated with a project whose purpose is to improve, enhance, or modernize that entity.
-
D.
hasFeatureCode
Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
-
E.
hasEditionFeature
Indicates that one edition of a work includes a specific feature, characteristic, or component that distinguishes it from other editions.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:41 p.m.