Triple
T32126964
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salem Unit 2 |
E820526
|
entity |
| Predicate | hasTurbineManufacturer |
P89014
|
FINISHED |
| Object | Westinghouse Electric Company |
—
|
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: Westinghouse Electric Company | Statement: [Salem Unit 2, hasTurbineManufacturer, Westinghouse Electric Company]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTurbineManufacturer Context triple: [Salem Unit 2, hasTurbineManufacturer, Westinghouse Electric Company]
-
A.
hasTurbineSupplier
chosen
Indicates that an entity has a specific supplier responsible for providing its turbine(s).
-
B.
hasTurbines
Indicates that one entity is equipped with, contains, or includes one or more turbines in relation to another entity.
-
C.
turbineType
Indicates the specific kind or category of turbine associated with or used by an entity.
-
D.
powerplantManufacturer
Indicates that one entity is the company or organization responsible for manufacturing or producing the power plant associated with another entity.
-
E.
hasTurbineHall
Indicates that something includes or is equipped with a turbine hall as part of its structure or facilities.
- 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_69f34902d42c819083a8e6bba9a8bb9a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b96c2f0881908d14683ecfe1af4b |
completed | May 3, 2026, 2:56 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:29 a.m.