Triple

T26157868
Position Surface form Disambiguated ID Type / Status
Subject Enoggera Creek E660015 entity
Predicate crossedBy P416 FINISHED
Object Kelvin Grove Road
Kelvin Grove Road is a major arterial road in Brisbane, Queensland, Australia, connecting the inner-city suburb of Kelvin Grove with the central business district and surrounding areas.
E2289742 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: Kelvin Grove Road | Statement: [Enoggera Creek, crossedBy, Kelvin Grove 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: Kelvin Grove Road
Triple: [Enoggera Creek, crossedBy, Kelvin Grove Road]
Generated description
Kelvin Grove Road is a major arterial road in Brisbane, Queensland, Australia, connecting the inner-city suburb of Kelvin Grove with the central business district and surrounding areas.

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_69ee5bc5a9908190899d39ce95c6d215 completed April 26, 2026, 6:39 p.m.
NER Named-entity recognition batch_69f60c12d3708190ac08d8b7c8ff48a5 completed May 2, 2026, 2:37 p.m.
NED1 Entity disambiguation (via context triple) batch_6a5b66d3195c81908f45f41440eced22 completed July 18, 2026, 11:43 a.m.
NEDg Description generation batch_6a5b675ecbc081909753aff758ef3576 completed July 18, 2026, 11:45 a.m.
NED2 Entity disambiguation (via description) batch_6a5b68075c2c819089e91500f6b23df0 completed July 18, 2026, 11:48 a.m.
Created at: April 26, 2026, 8:28 p.m.