Triple

T36844677
Position Surface form Disambiguated ID Type / Status
Subject Kāpiti Expressway E910508 entity
Predicate hasJunctionWith P1018 FINISHED
Object Peka Peka Road
Peka Peka Road is a local road in the Kāpiti Coast district of New Zealand that connects the rural Peka Peka area to the region’s main transport routes.
E2247672 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: Peka Peka Road | Statement: [Kāpiti Expressway, hasJunctionWith, Peka Peka Road]
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: Peka Peka Road
Triple: [Kāpiti Expressway, hasJunctionWith, Peka Peka Road]
Generated description
Peka Peka Road is a local road in the Kāpiti Coast district of New Zealand that connects the rural Peka Peka area to the region’s main transport routes.

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_69f76e7f65a881908651b702da592b6d completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69f7cfa643a481908bbaef04266a6931 completed May 3, 2026, 10:43 p.m.
NED1 Entity disambiguation (via context triple) batch_6a4103ffc4e88190a491a7e287ba2ecf completed June 28, 2026, 11:22 a.m.
NEDg Description generation batch_6a410817c2888190ac2cccd99b964ebc completed June 28, 2026, 11:40 a.m.
NED2 Entity disambiguation (via description) batch_6a41088f75a481908bf5c65c577c21a5 completed June 28, 2026, 11:42 a.m.
Created at: May 3, 2026, 4:13 p.m.