Triple

T30874449
Position Surface form Disambiguated ID Type / Status
Subject Ada E786435 entity
Predicate governingBody P46 FINISHED
Object Municipality of Ada
The Municipality of Ada is the local self-government authority responsible for administering public services, development, and governance in the town and surrounding area of Ada.
E1936589 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: Municipality of Ada | Statement: [Ada, governingBody, Municipality of Ada]
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: Municipality of Ada
Triple: [Ada, governingBody, Municipality of Ada]
Generated description
The Municipality of Ada is the local self-government authority responsible for administering public services, development, and governance in the town and surrounding area of Ada.

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_69f224bae17c8190bb3a6a28e3d019df completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f691d56ec081909265c4b014388243 completed May 3, 2026, 12:07 a.m.
NED1 Entity disambiguation (via context triple) batch_6a28c7de0fa48190b703a2e70f24ea8a completed June 10, 2026, 2:11 a.m.
NEDg Description generation batch_6a28cc923acc8190a523d041f105e029 completed June 10, 2026, 2:31 a.m.
NED2 Entity disambiguation (via description) batch_6a28cd47f3a08190a9e52113a7b664f1 completed June 10, 2026, 2:34 a.m.
Created at: April 29, 2026, 8:48 p.m.