Triple
T28241007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Copeton Dam |
E712023
|
entity |
| Predicate | stateParkOperator |
P183990
|
FINISHED |
| Object | NSW National Parks and Wildlife Service |
—
|
NE NERFINISHED |
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: NSW National Parks and Wildlife Service | Statement: [Copeton Dam, stateParkOperator, NSW National Parks and Wildlife Service]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateParkOperator Context triple: [Copeton Dam, stateParkOperator, NSW National Parks and Wildlife Service]
-
A.
stateParkSystem
Indicates that an entity is part of, managed by, or associated with a state-level park system or network of state parks.
-
B.
stateParkLocation
Indicates that a state park is located within or associated with a specific geographic place or administrative region.
-
C.
nationalParkAccess
Indicates that one entity has the right, ability, or permission to enter, use, or benefit from a specified national park.
-
D.
skiResortOperator
Indicates that an entity operates, manages, or runs a ski resort for another entity or location.
-
E.
servesNationalPark
Indicates that an entity provides services or functions in support of a national park.
- F. None of above. chosen
Provenance (4 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_69efb51fb98881909692421959ec0170 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f7aaabb58c8190bf81673608ecfb6e |
completed | May 3, 2026, 8:06 p.m. |
| PD | Predicate disambiguation | batch_69f7a8cec6d48190bebfa884b2f938c0 |
completed | May 3, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f7aa6795f481908940838ee7041ff5 |
completed | May 3, 2026, 8:04 p.m. |
Created at: April 27, 2026, 10:58 p.m.