Triple

T38552563
Position Surface form Disambiguated ID Type / Status
Subject John of Montfort E925150 entity
Predicate alsoKnownAs P39 FINISHED
Object Jean de Bretagne
Jean de Bretagne, also known as John of Montfort, was a 14th-century nobleman who played a central role in the Breton War of Succession over the Duchy of Brittany.
E2285837 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: Jean de Bretagne | Statement: [John of Montfort, alsoKnownAs, Jean de Bretagne]
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: Jean de Bretagne
Triple: [John of Montfort, alsoKnownAs, Jean de Bretagne]
Generated description
Jean de Bretagne, also known as John of Montfort, was a 14th-century nobleman who played a central role in the Breton War of Succession over the Duchy of Brittany.

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_69f76eaeb69c8190b367df9330d6f6af completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fcd318ae38819092ebab2d75be2194 completed May 7, 2026, 5:59 p.m.
NED1 Entity disambiguation (via context triple) batch_6a46295350388190ac9ff1f90e86ad9b completed July 2, 2026, 9:03 a.m.
NEDg Description generation batch_6a4629fc2bb081909ec341ec88147bcc completed July 2, 2026, 9:06 a.m.
NED2 Entity disambiguation (via description) batch_6a462b7b5be48190852a5802842f86f9 completed July 2, 2026, 9:12 a.m.
Created at: May 3, 2026, 4:32 p.m.