Triple

T32586287
Position Surface form Disambiguated ID Type / Status
Subject Moriyama city government E832929 entity
Predicate hasBranch P35 FINISHED
Object Moriyama city council
Moriyama city council is the elected legislative body responsible for making local laws, policies, and budget decisions for the city of Moriyama in Japan.
E832929 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: Moriyama city council | Statement: [Moriyama city government, hasBranch, Moriyama city council]
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: Moriyama city council
Triple: [Moriyama city government, hasBranch, Moriyama city council]
Generated description
Moriyama city council is the elected legislative body responsible for making local laws, policies, and budget decisions for the city of Moriyama in Japan.

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_69f34929ff648190aded9424aa7564ae completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69f6c66df4f48190b118f51553cd8437 completed May 3, 2026, 3:52 a.m.
NED1 Entity disambiguation (via context triple) batch_6a347ba8c47481908eac2a95efef46bb completed June 18, 2026, 11:13 p.m.
NEDg Description generation batch_6a347c9f8bc48190b83503d479a75958 completed June 18, 2026, 11:17 p.m.
NED2 Entity disambiguation (via description) batch_6a347d6a097881909f078a5dbbdf4e1f completed June 18, 2026, 11:21 p.m.
Created at: May 1, 2026, 1:04 a.m.