Triple

T32000539
Position Surface form Disambiguated ID Type / Status
Subject Somerton City Council E817113 entity
Predicate jurisdiction P82 FINISHED
Object City of Somerton
The City of Somerton is a local government area administered by the Somerton City Council, providing municipal services and governance for its community.
E1986870 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: City of Somerton | Statement: [Somerton City Council, jurisdiction, City of Somerton]
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: City of Somerton
Triple: [Somerton City Council, jurisdiction, City of Somerton]
Generated description
The City of Somerton is a local government area administered by the Somerton City Council, providing municipal services and governance for its community.

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_69f348f8ce388190ae84376b1f348f12 completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6b3fbfe4c8190bc1591394bc8ebb4 completed May 3, 2026, 2:33 a.m.
NED1 Entity disambiguation (via context triple) batch_6a2eb16123908190a1248821d97424ba completed June 14, 2026, 1:49 p.m.
NEDg Description generation batch_6a2eb2dc4ea88190b36019319ca4acdd completed June 14, 2026, 1:55 p.m.
NED2 Entity disambiguation (via description) batch_6a2eb375928881909f4acfa17204fab5 completed June 14, 2026, 1:58 p.m.
Created at: May 1, 2026, 12:14 a.m.