Triple

T35579484
Position Surface form Disambiguated ID Type / Status
Subject Currimundi Lake E1028178 entity
Predicate adjacentTo P224 FINISHED
Object Currimundi suburb
Currimundi suburb is a coastal residential area on Queensland’s Sunshine Coast known for its family-friendly atmosphere, beaches, and proximity to Currimundi Lake.
E2146430 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: Currimundi suburb | Statement: [Currimundi Lake, adjacentTo, Currimundi suburb]
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: Currimundi suburb
Triple: [Currimundi Lake, adjacentTo, Currimundi suburb]
Generated description
Currimundi suburb is a coastal residential area on Queensland’s Sunshine Coast known for its family-friendly atmosphere, beaches, and proximity to Currimundi Lake.

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_69f76e0386688190b931bacdc145938c completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69f79e826f248190a8b8e9344f3f15fc completed May 3, 2026, 7:14 p.m.
NED1 Entity disambiguation (via context triple) batch_6a385309a6d88190a67b45538d23478d completed June 21, 2026, 9:09 p.m.
NEDg Description generation batch_6a385475674c8190866dd53e47dac3bd completed June 21, 2026, 9:15 p.m.
NED2 Entity disambiguation (via description) batch_6a38552e7974819082b7ee16b00a21d0 completed June 21, 2026, 9:18 p.m.
Created at: May 3, 2026, 4:04 p.m.