Triple

T17955317
Position Surface form Disambiguated ID Type / Status
Subject Rodolphe Kreutzer E448930 entity
Predicate givenName P17 FINISHED
Object Rodolphe NE NERFINISHED

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: Rodolphe | Statement: [Rodolphe Kreutzer, givenName, Rodolphe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Rodolphe
Context triple: [Rodolphe Kreutzer, givenName, Rodolphe]
  • A. Rodolphe chosen
    Rodolphe is a masculine given name of French origin, historically borne by several notable European artists, writers, and public figures.
  • B. Adolphe
    Adolphe is the given name of Jean-Charles Adolphe Alphand, a prominent 19th-century French engineer known for designing many of Paris’s parks and boulevards.
  • C. Amédée
    Amédée is a given name of French usage, corresponding to the Italian name Amedeo and ultimately derived from the Latin Amadeus.
  • D. René
    René is a French given name commonly used for males and historically associated with several notable figures in politics, arts, and philosophy.
  • E. Gustave
    Gustave is a masculine given name of French origin, famously borne by engineer Gustave Eiffel.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8b9f8cca8819099836916c56b7c95 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4afafe814819085300163f73de5f2 completed April 19, 2026, 10:34 a.m.
Created at: April 10, 2026, 10:21 a.m.