Triple

T29865863
Position Surface form Disambiguated ID Type / Status
Subject Rinus E758454 entity
Predicate hasNotableBearer P458 FINISHED
Object Rinus Ferdinandusse
Rinus Ferdinandusse was a Dutch journalist, writer, and long-time editor-in-chief of the magazine Vrij Nederland, known for his influential role in postwar Dutch media and culture.
E1895254 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: Rinus Ferdinandusse | Statement: [Rinus, hasNotableBearer, Rinus Ferdinandusse]
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: Rinus Ferdinandusse
Triple: [Rinus, hasNotableBearer, Rinus Ferdinandusse]
Generated description
Rinus Ferdinandusse was a Dutch journalist, writer, and long-time editor-in-chief of the magazine Vrij Nederland, known for his influential role in postwar Dutch media and culture.

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_69f2245b4dec8190b85f664d918a00a5 completed April 29, 2026, 3:31 p.m.
NER Named-entity recognition batch_69f67689a3908190bdef1a1108f42f87 completed May 2, 2026, 10:11 p.m.
NED1 Entity disambiguation (via context triple) batch_6a2721e018fc8190a4178ba0079ffb52 completed June 8, 2026, 8:11 p.m.
NEDg Description generation batch_6a272600dcdc8190905cfeee767fd5d1 completed June 8, 2026, 8:28 p.m.
NED2 Entity disambiguation (via description) batch_6a272657902c8190b575bad27649a760 completed June 8, 2026, 8:30 p.m.
Created at: April 29, 2026, 5:51 p.m.