Triple
T10109147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kirov-class battlecruiser |
E218196
|
entity |
| Predicate | secondaryPropulsion |
P21496
|
FINISHED |
| Object | steam turbines |
—
|
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: steam turbines | Statement: [Kirov-class battlecruiser, secondaryPropulsion, steam turbines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryPropulsion Context triple: [Kirov-class battlecruiser, secondaryPropulsion, steam turbines]
-
A.
auxiliaryPropulsion
chosen
Indicates that an entity provides secondary or backup propulsion support to another entity or system.
-
B.
laterPropulsion
Indicates that one propulsion system, method, or event occurs after another in time.
-
C.
propulsion
Indicates a relationship where one entity provides the driving force or thrust that moves another entity forward or keeps it in motion.
-
D.
originalPropulsion
Indicates that one entity serves as the initial or native means of propulsion or movement for another entity.
-
E.
propulsionFeature
Indicates a relationship where a propulsion-related characteristic or capability is attributed to an entity.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd0cbd8a48190b2af6177d1249f58 |
completed | April 2, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9ed7e48190aa132ef8a69b49f9 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:03 p.m.