Triple
T14153912
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bogong Peaks Wilderness Area |
E350759
|
entity |
| Predicate | zoningWithinPark |
P113031
|
FINISHED |
| Object | wilderness zone |
—
|
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: wilderness zone | Statement: [Bogong Peaks Wilderness Area, zoningWithinPark, wilderness zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: zoningWithinPark Context triple: [Bogong Peaks Wilderness Area, zoningWithinPark, wilderness zone]
-
A.
isWithinPark
Indicates that one entity is located inside the boundaries of a park that contains it.
-
B.
isWithinParkSystem
Indicates that one area, facility, or feature is located inside and belongs to a designated park system.
-
C.
withinNationalPark
Indicates that one entity is located inside the geographic boundaries of a national park designated by another entity.
-
D.
withinRecreationArea
Indicates that one entity is located inside the spatial bounds of a designated recreation area associated with another entity.
-
E.
locatedInParkVicinity
Indicates that an entity is situated in the area immediately surrounding or near a 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6133754881908e1e97db71772deb |
completed | April 14, 2026, 3:45 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
| PDg | Predicate description generation | batch_69de239a02e881909b0e2679487e4ab2 |
completed | April 14, 2026, 11:23 a.m. |
Created at: April 10, 2026, 12:58 a.m.