Triple
T24006716
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lake Hāwea |
E594407
|
entity |
| Predicate | hasRecreationReserve |
P114925
|
FINISHED |
| Object | Lake Hāwea Domain |
—
|
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: Lake Hāwea Domain | Statement: [Lake Hāwea, hasRecreationReserve, Lake Hāwea Domain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecreationReserve Context triple: [Lake Hāwea, hasRecreationReserve, Lake Hāwea Domain]
-
A.
hasRecreationProvider
Indicates that an entity offers or supplies recreational services, facilities, or activities to another entity.
-
B.
hasRecreationPurpose
Indicates that something is used or intended to be used for recreational or leisure activities.
-
C.
hasRecreationSection
chosen
Indicates that an entity includes or is associated with a designated recreation section or recreational area.
-
D.
hasRecreationFacility
Indicates that one entity provides, contains, or is equipped with a recreational facility for use by another entity or by the public.
-
E.
hasRecreationHub
Indicates that an entity serves as or is associated with a central place or facility for recreational activities for another entity.
- 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_69e288b9ecf08190b8c94a278f5674fe |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d46a6ba48190b0cce0b134dfb35f |
completed | April 29, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:40 p.m.