Triple
T4491458
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liddell Power Station |
E100581
|
entity |
| Predicate | hasAshDisposalFacility |
P12416
|
FINISHED |
| Object | ash dam |
—
|
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: ash dam | Statement: [Liddell Power Station, hasAshDisposalFacility, ash dam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAshDisposalFacility Context triple: [Liddell Power Station, hasAshDisposalFacility, ash dam]
-
A.
hasTrashReceptacles
Indicates that one entity provides, contains, or is equipped with trash receptacles for waste disposal in relation to another entity or location.
-
B.
landfilledFrom
Indicates that material, waste, or items originate from a specified source and are disposed of by being placed into a landfill at the target location.
-
C.
methodOfDisposal
Indicates the specific way or process by which something is discarded, eliminated, or otherwise gotten rid of.
-
D.
hasDropOffArea
Indicates that an entity provides a designated area where items, passengers, or goods can be temporarily left or unloaded.
-
E.
hasFacilities
chosen
Indicates that an entity possesses, provides, or is equipped with certain facilities or physical resources.
- 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_69bd43cdf15081909a4fa2585ff63b3e |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd556e69f88190b9c16afc2afcdbef |
completed | March 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69bd5213e3d0819094b026989e686f01 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 12:59 p.m.