Triple
T37871536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Convair 580 |
E944616
|
entity |
| Predicate | powerplantUpgradeFrom |
P193167
|
FINISHED |
| Object | Pratt & Whitney R‑2800 radial engines |
—
|
NE NERFINISHED |
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: Pratt & Whitney R‑2800 radial engines | Statement: [Convair 580, powerplantUpgradeFrom, Pratt & Whitney R‑2800 radial engines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerplantUpgradeFrom Context triple: [Convair 580, powerplantUpgradeFrom, Pratt & Whitney R‑2800 radial engines]
-
A.
powerplantUpgradeComparedTo
Indicates a comparison between two entities regarding the extent or nature of an upgrade made to their power plants.
-
B.
powerplantAdvantage
Indicates that one power plant has an advantage or beneficial characteristic over another in a given context.
-
C.
upgradeOf
Indicates that one entity is a newer, improved, or more advanced version of another entity.
-
D.
powerplantVariant
Indicates that one power plant is a specific version, configuration, or model variant of another power plant design.
-
E.
powerplantFor
Indicates that one entity functions as the power plant or primary energy source serving another entity.
- F. None of above. chosen
Provenance (4 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fd389cb28c819099a77e28d25f258a |
completed | May 8, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69fd3826d8048190ada79a5868d1d7f3 |
completed | May 8, 2026, 1:11 a.m. |
| PDg | Predicate description generation | batch_69fd389b653c81908a97ab2eff98c6ea |
completed | May 8, 2026, 1:12 a.m. |
Created at: May 3, 2026, 4:19 p.m.