Triple

T37619533
Position Surface form Disambiguated ID Type / Status
Subject Count of Montmorency E936023 entity
Predicate linkedToTerritory P21614 FINISHED
Object County of Montmorency
The County of Montmorency was a prominent medieval French territorial lordship associated with the influential Montmorency noble family near Paris.
E2235352 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: County of Montmorency | Statement: [Count of Montmorency, linkedToTerritory, County of Montmorency]
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: County of Montmorency
Triple: [Count of Montmorency, linkedToTerritory, County of Montmorency]
Generated description
The County of Montmorency was a prominent medieval French territorial lordship associated with the influential Montmorency noble family near Paris.

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_69f76ed16b748190ad6add183b1be688 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fba92fe9e0819082779371e7d4a205 completed May 6, 2026, 8:48 p.m.
NED1 Entity disambiguation (via context triple) batch_6a40afeaf43081908553c644b27a6a14 completed June 28, 2026, 5:23 a.m.
NEDg Description generation batch_6a40b092e2a8819090f6f444992bdcff completed June 28, 2026, 5:26 a.m.
NED2 Entity disambiguation (via description) batch_6a40b0f1db0c8190ac485f992c9ac90f completed June 28, 2026, 5:28 a.m.
Created at: May 3, 2026, 4:18 p.m.