Triple
T36941130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Te Whanganui-a-Tara region |
E913766
|
entity |
| Predicate | containsRegionalPark |
P19165
|
FINISHED |
| Object | Belmont Regional Park |
—
|
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: Belmont Regional Park | Statement: [Te Whanganui-a-Tara region, containsRegionalPark, Belmont Regional Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsRegionalPark Context triple: [Te Whanganui-a-Tara region, containsRegionalPark, Belmont Regional Park]
-
A.
hasRegionalPark
chosen
Indicates that a place or administrative area contains or is served by a designated regional park.
-
B.
containsProvincialPark
Indicates that one entity geographically includes or encompasses a provincial park within its boundaries.
-
C.
containsNaturalPark
Indicates that one entity geographically includes or encompasses a natural park within its boundaries.
-
D.
locatedInNationalOrProvincialPark
Indicates that one entity is situated within the boundaries of a national or provincial park.
-
E.
regionOfPark
Indicates that one entity is a geographic or administrative region that contains or is designated as a specific park.
- 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_69f76e8a6a5c81909c1febf32bf3fe23 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a016336c58081909c58c5772e6fb488 |
completed | May 11, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a0160f25d8081909a6aaa375e9850b0 |
completed | May 11, 2026, 4:54 a.m. |
Created at: May 3, 2026, 4:13 p.m.