Triple

T21678153
Position Surface form Disambiguated ID Type / Status
Subject Henderson, Auckland, New Zealand E535027 entity
Predicate hasPark P105 FINISHED
Object Henderson Park
Henderson Park is a public green space in the Auckland suburb of Henderson, featuring walking paths, sports facilities, and riverside areas for recreation.
E1940607 NE 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: Henderson Park | Statement: [Henderson, Auckland, New Zealand, hasPark, Henderson Park]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Henderson Park
Triple: [Henderson, Auckland, New Zealand, hasPark, Henderson Park]
Generated description
Henderson Park is a public green space in the Auckland suburb of Henderson, featuring walking paths, sports facilities, and riverside areas for recreation.

Provenance (5 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_69e0c469b6ec8190aee4cadd1527db91 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69ef8a11088081908911af2629f54c1c completed April 27, 2026, 4:08 p.m.
NED1 Entity disambiguation (via context triple) batch_6a28fb843dc88190bc6b421c9ed6fde1 completed June 10, 2026, 5:52 a.m.
NEDg Description generation batch_6a28ffc3037481909e380c0b60ebce5c completed June 10, 2026, 6:10 a.m.
NED2 Entity disambiguation (via description) batch_6a29005bb6bc81909fa20caeb92ac2be completed June 10, 2026, 6:12 a.m.
Created at: April 16, 2026, 6:43 p.m.