Triple

T33514315
Position Surface form Disambiguated ID Type / Status
Subject Pippin of Landen E858325 entity
Predicate alsoKnownAs P39 FINISHED
Object Pippin I of Landen
Pippin I of Landen was a 7th-century Frankish nobleman who served as Mayor of the Palace of Austrasia and became a key ancestor of the Carolingian dynasty.
E2085958 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: Pippin I of Landen | Statement: [Pippin of Landen, alsoKnownAs, Pippin I of Landen]
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: Pippin I of Landen
Triple: [Pippin of Landen, alsoKnownAs, Pippin I of Landen]
Generated description
Pippin I of Landen was a 7th-century Frankish nobleman who served as Mayor of the Palace of Austrasia and became a key ancestor of the Carolingian dynasty.

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_69f3497721848190978fbee5e0a526f8 completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69f6f6740f1c8190ad5a5dfab497d956 completed May 3, 2026, 7:17 a.m.
NED1 Entity disambiguation (via context triple) batch_6a36cc624d50819082df15d9a7ab7d86 completed June 20, 2026, 5:22 p.m.
NEDg Description generation batch_6a36cd5b9ff48190b9e6d76abfff3295 completed June 20, 2026, 5:26 p.m.
NED2 Entity disambiguation (via description) batch_6a36ce3e3e48819091aece379948e411 completed June 20, 2026, 5:30 p.m.
Created at: May 1, 2026, 1:39 a.m.