Triple
T17870576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NEM New South Wales region |
E446824
|
entity |
| Predicate | tradingArrangement |
P28271
|
FINISHED |
| Object | gross pool market |
—
|
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: gross pool market | Statement: [NEM New South Wales region, tradingArrangement, gross pool market]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tradingArrangement Context triple: [NEM New South Wales region, tradingArrangement, gross pool market]
-
A.
trades
Indicates an exchange relationship where one party gives something of value to another in return for something else of value.
-
B.
tradeSystem
chosen
Indicates a system or framework through which goods, services, or assets are exchanged between parties under defined rules or mechanisms.
-
C.
tradeMechanism
Indicates the method or system through which a trade or exchange between parties is conducted.
-
D.
tradesAs
Indicates that one entity conducts business or is publicly known under the trading name or brand of another entity.
-
E.
tradesInstrument
Indicates that one party engages in buying, selling, or exchanging a specified financial or tradable instrument.
- 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_69d8b9f4c22c819093c2680434472894 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e49aa24c8481909de38953a88ff615 |
completed | April 19, 2026, 9:04 a.m. |
| PD | Predicate disambiguation | batch_69e3d8e6d2e88190ad9ef9f8a99f13e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:18 a.m.