Triple

T35091030
Position Surface form Disambiguated ID Type / Status
Subject Morainvilliers E1012722 entity
Predicate partOf P40 FINISHED
Object canton of Poissy
The canton of Poissy is an administrative division in the Yvelines department of north-central France, centered on the town of Poissy and grouping several surrounding communes.
E2125864 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: canton of Poissy | Statement: [Morainvilliers, partOf, canton of Poissy]
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: canton of Poissy
Triple: [Morainvilliers, partOf, canton of Poissy]
Generated description
The canton of Poissy is an administrative division in the Yvelines department of north-central France, centered on the town of Poissy and grouping several surrounding communes.

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_69f76dd432ec8190969bc32acfc152b1 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f78bdc662081909928c6a449e6c134 completed May 3, 2026, 5:54 p.m.
NED1 Entity disambiguation (via context triple) batch_6a37cfed93488190b58b8f50675227d0 completed June 21, 2026, 11:50 a.m.
NEDg Description generation batch_6a37d07ba708819081b552b8a69313e5 completed June 21, 2026, 11:52 a.m.
NED2 Entity disambiguation (via description) batch_6a37d1935d9881909cee3755fec2d996 completed June 21, 2026, 11:57 a.m.
Created at: May 3, 2026, 4:01 p.m.