Triple
T14615781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tumut 3 Power Station |
E343080
|
entity |
| Predicate | hasUndergroundCavern |
P10755
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tumut 3 Power Station, hasUndergroundCavern, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUndergroundCavern Context triple: [Tumut 3 Power Station, hasUndergroundCavern, yes]
-
A.
hasCaves
chosen
Indicates that one entity possesses, contains, or is characterized by the presence of caves.
-
B.
hasUndergroundMine
Indicates that one entity possesses, controls, or contains an underground mine associated with it.
-
C.
hasNearbyCave
Indicates that one entity is located close to or in the vicinity of a cave associated with another entity.
-
D.
undergroundCavernLength
Indicates the measured linear extent or distance from one end to the other of an underground cavern.
-
E.
hasLowerCave
Indicates that one location or structure possesses or is associated with another cave situated at a lower level or beneath it.
- 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.