Triple
T3310080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ilyushin Il-2 |
E69549
|
entity |
| Predicate | powerplantPower |
P47194
|
FINISHED |
| Object | 1700 hp |
—
|
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: 1700 hp | Statement: [Ilyushin Il-2, powerplantPower, 1700 hp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerplantPower Context triple: [Ilyushin Il-2, powerplantPower, 1700 hp]
-
A.
powerplant
Indicates that an entity functions as a facility or installation where energy sources are converted into usable power, typically electricity.
-
B.
powerplantOutput
Indicates the amount of energy or power produced by a power plant over a given period or at a specific moment.
-
C.
powerplantFor
Indicates that one entity functions as the power plant or primary energy source serving another entity.
-
D.
powerplantType
Indicates the specific kind or category of power plant associated with an entity, based on how it generates energy.
-
E.
powerplantRole
Indicates that one entity serves in a specific functional or operational role relative to a power plant.
- 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_69ad859f218081909458d2cebbf57565 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb0eb6dd08190bab1ce80f417966a |
completed | March 8, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69ada4282730819092aa39c5f9269df0 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada52716ec81908e89688a81039394 |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:11 p.m.