Triple
T31999604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rata |
E817086
|
entity |
| Predicate | associatedWithPowerplant |
P17850
|
FINISHED |
| Object | Shvetsov radial engine |
E1252943
|
NE 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: Shvetsov radial engine | Statement: [Rata, associatedWithPowerplant, Shvetsov radial engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithPowerplant Context triple: [Rata, associatedWithPowerplant, Shvetsov radial engine]
-
A.
powerplantFor
chosen
Indicates that one entity functions as the power plant or primary energy source serving another entity.
-
B.
powerplantForRole
Indicates that a power plant serves or is designated to fulfill a specific functional role or responsibility.
-
C.
powerplantPower
Indicates that a power plant provides or generates a specified amount of electrical power.
-
D.
usedPowerplantsFrom
Indicates that an entity has utilized or drawn energy from the specified power plants.
-
E.
powerplantRole
Indicates that one entity serves in a specific functional or operational role relative to a power plant.
- F. None of above.
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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2eb16123908190a1248821d97424ba |
completed | June 14, 2026, 1:49 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:14 a.m.