Triple

T25318812
Position Surface form Disambiguated ID Type / Status
Subject Sydney Harbour Federation Trust E634820 entity
Predicate appliesToJurisdiction P82 FINISHED
Object Sydney
Sydney is Australia’s largest and most populous city, renowned for its iconic harbour, cultural diversity, and role as a major economic and tourist hub.
E8462 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: Sydney | Statement: [Sydney Harbour Federation Trust, appliesToJurisdiction, Sydney]
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: Sydney
Triple: [Sydney Harbour Federation Trust, appliesToJurisdiction, Sydney]
Generated description
Sydney is Australia’s largest and most populous city, renowned for its iconic harbour, cultural diversity, and role as a major economic and tourist hub.

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_69e75a9847c08190bb02990d06d5ffb7 completed April 21, 2026, 11:08 a.m.
NER Named-entity recognition batch_69f4968bc24c81909d8b9f0df2704210 completed May 1, 2026, 12:03 p.m.
NED1 Entity disambiguation (via context triple) batch_6a10b715795481908c338dafa4a23eeb completed May 22, 2026, 8:05 p.m.
NEDg Description generation batch_6a10b9966114819093e81a647905346a completed May 22, 2026, 8:16 p.m.
NED2 Entity disambiguation (via description) batch_6a10ba344df081908266aaa1920d9f3d completed May 22, 2026, 8:19 p.m.
Created at: April 21, 2026, 1:28 p.m.