Triple

T25024640
Position Surface form Disambiguated ID Type / Status
Subject London Circuit, Canberra E626674 entity
Predicate hasNearbyLandmark P2064 FINISHED
Object Civic Square
Civic Square is a prominent public and cultural precinct in central Canberra that houses key civic buildings, artworks, and open spaces used for community events and gatherings.
E1671894 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: Civic Square | Statement: [London Circuit, Canberra, hasNearbyLandmark, Civic Square]
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: Civic Square
Triple: [London Circuit, Canberra, hasNearbyLandmark, Civic Square]
Generated description
Civic Square is a prominent public and cultural precinct in central Canberra that houses key civic buildings, artworks, and open spaces used for community events and gatherings.

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_69e2ff28ee3881909c626af002457a4a completed April 18, 2026, 3:48 a.m.
NER Named-entity recognition batch_69f44f68c3108190a84604ae5d015d84 completed May 1, 2026, 6:59 a.m.
NED1 Entity disambiguation (via context triple) batch_6a1067b1c4608190bc713bd23b78c9b2 completed May 22, 2026, 2:26 p.m.
NEDg Description generation batch_6a1068d5ff248190b9efb77366147c26 completed May 22, 2026, 2:31 p.m.
NED2 Entity disambiguation (via description) batch_6a1069cb170c8190b31daf74fff26c35 completed May 22, 2026, 2:35 p.m.
Created at: April 18, 2026, 6:07 a.m.