Triple

T38513074
Position Surface form Disambiguated ID Type / Status
Subject Cranbrook, Queensland E921964 entity
Predicate roadBoundary P67275 FINISHED
Object Dalrymple Road
Dalrymple Road is a significant local roadway in Cranbrook, a suburb of Townsville in Queensland, Australia, serving as a key boundary and access route for the area.
E2297955 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: Dalrymple Road | Statement: [Cranbrook, Queensland, roadBoundary, Dalrymple 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: Dalrymple Road
Triple: [Cranbrook, Queensland, roadBoundary, Dalrymple Road]
Generated description
Dalrymple Road is a significant local roadway in Cranbrook, a suburb of Townsville in Queensland, Australia, serving as a key boundary and access route for the area.

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_69f76ea3c5448190aa7002fc1ba3f874 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fcd28e4d68819083ea0fa4a731fa43 completed May 7, 2026, 5:57 p.m.
NED1 Entity disambiguation (via context triple) batch_6a840c5270a48190beff85359f488066 completed Aug. 18, 2026, 7:40 a.m.
NEDg Description generation batch_6a840d41c6108190bf5b9effe30a7b2d completed Aug. 18, 2026, 7:44 a.m.
NED2 Entity disambiguation (via description) batch_6a840e3464488190b34a2678f8dd17ae completed Aug. 18, 2026, 7:48 a.m.
Created at: May 3, 2026, 4:32 p.m.