Triple
T14615776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tumut 3 Power Station |
E343080
|
entity |
| Predicate | gridSupportFunction |
P101005
|
FINISHED |
| Object | frequency control |
—
|
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: frequency control | Statement: [Tumut 3 Power Station, gridSupportFunction, frequency control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gridSupportFunction Context triple: [Tumut 3 Power Station, gridSupportFunction, frequency control]
-
A.
supportFunction
chosen
Indicates that one entity provides assistance, resources, or functionality that enables or enhances the operation or effectiveness of another entity.
-
B.
providesSupportTo
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
-
C.
layoutSupport
Indicates that one entity provides or enables structural or spatial arrangement capabilities for another entity.
-
D.
mappingSupportBy
Indicates that one entity provides support, resources, or functionality enabling another entity to perform or maintain a mapping between elements.
-
E.
frameworkSupport
Indicates that one entity provides compatibility with, or operational support for, a particular framework used by 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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb46439b88190a4affcc7ccedab6b |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
Created at: April 10, 2026, 1:25 a.m.