Triple
T4476602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wright R-3350 Duplex-Cyclone |
E100022
|
entity |
| Predicate | laterVariantFeature |
P52452
|
FINISHED |
| Object | turbo-compound power-recovery 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: turbo-compound power-recovery turbines | Statement: [Wright R-3350 Duplex-Cyclone, laterVariantFeature, turbo-compound power-recovery turbines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterVariantFeature Context triple: [Wright R-3350 Duplex-Cyclone, laterVariantFeature, turbo-compound power-recovery turbines]
-
A.
laterFeature
chosen
Indicates that one feature, event, or element occurs or is introduced after another in time.
-
B.
variant
Indicates that one entity is an alternative form, version, or variation of another entity.
-
C.
laterVersion
Indicates that one entity is a subsequent or more recent version of another entity in a version sequence.
-
D.
affectsVariant
Indicates that one entity has an influence or impact on a specific variant or version of another entity.
-
E.
laterModification
Indicates that one entity is a modification or revision that occurs after another in time.
- 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_69b34553cbe48190afa8ac1cac285b86 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35728ed508190ba0e882fa62d8848 |
completed | March 13, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69b3563d63008190816e37027e761375 |
completed | March 13, 2026, 12:11 a.m. |
Created at: March 12, 2026, 11:35 p.m.