Triple
T23832105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Grande-3 generating station |
E589539
|
entity |
| Predicate | usesGeneratorType |
P75139
|
FINISHED |
| Object | synchronous generator |
—
|
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: synchronous generator | Statement: [La Grande-3 generating station, usesGeneratorType, synchronous generator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGeneratorType Context triple: [La Grande-3 generating station, usesGeneratorType, synchronous generator]
-
A.
hasGeneratorType
chosen
Indicates that an entity is associated with or uses a specific type or category of generator.
-
B.
hasTypeOfGeneration
Indicates that one entity is characterized by or associated with a particular kind or method of generation.
-
C.
hasTypeGenus
Indicates that one entity is the type genus that formally defines or represents the taxonomic group of the other entity.
-
D.
usesCircuitType
Indicates that one entity employs or is implemented using a specific type of circuit.
-
E.
hasGeneratingFunction
Indicates that one entity serves as the generating function associated with, or defining, another entity.
- 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_69e25d1922d481909cab567c06a802ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7f6f25c8190bd8957fe3cbefc03 |
completed | April 29, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8:05 p.m.