Triple
T35062713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beauharnois |
E1011636
|
entity |
| Predicate | operatorOfMajorFacility |
P4904
|
FINISHED |
| Object | Hydro-Québec |
—
|
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: Hydro-Québec | Statement: [Beauharnois, operatorOfMajorFacility, Hydro-Québec]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorOfMajorFacility Context triple: [Beauharnois, operatorOfMajorFacility, Hydro-Québec]
-
A.
isMajorFacilityOn
Indicates that a facility is a primary or significant installation located on or associated with a particular entity or site.
-
B.
operatesFacility
chosen
Indicates that an entity is responsible for running, managing, or controlling the operations of a particular facility.
-
C.
servesAsOperatorOf
Indicates that one entity functions as the operator or operating agent responsible for running, controlling, or managing another entity.
-
D.
regulatesFacility
Indicates that one entity has authority to control, oversee, or set rules governing the operation or behavior of a facility.
-
E.
isMajorFacadeOf
Indicates a relationship where one facade serves as the primary or most prominent exterior face of a building or structure.
- 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_69f76dd09c308190a523454853ce842b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a0123d1162c81908182d01ba3ddd236 |
completed | May 11, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_6a01236713d88190b12a567c0dfb2d49 |
completed | May 11, 2026, 12:31 a.m. |
Created at: May 3, 2026, 4:01 p.m.