Triple

T23660204
Position Surface form Disambiguated ID Type / Status
Subject Peseux E584421 entity
Predicate partOfAdministrativeUnit P3892 FINISHED
Object district of Neuchâtel
The district of Neuchâtel is an administrative subdivision in the Swiss canton of Neuchâtel that encompasses several municipalities, including Peseux.
E1713260 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: district of Neuchâtel | Statement: [Peseux, partOfAdministrativeUnit, district of Neuchâtel]
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: district of Neuchâtel
Triple: [Peseux, partOfAdministrativeUnit, district of Neuchâtel]
Generated description
The district of Neuchâtel is an administrative subdivision in the Swiss canton of Neuchâtel that encompasses several municipalities, including Peseux.

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_69e248ffc0888190ae23c4731eb8b7ac completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1b35f03448190834991c2a65ef0e4 completed April 29, 2026, 7:29 a.m.
NED1 Entity disambiguation (via context triple) batch_6a11853511dc81909a605092ff8ab837 completed May 23, 2026, 10:45 a.m.
NEDg Description generation batch_6a11861e622c8190a73ab247d696435a completed May 23, 2026, 10:49 a.m.
NED2 Entity disambiguation (via description) batch_6a1186c04c2c8190a5e70c9d9a5cbeb8 completed May 23, 2026, 10:51 a.m.
Created at: April 17, 2026, 6:50 p.m.