Triple

T20886830
Position Surface form Disambiguated ID Type / Status
Subject Jean-Charles Adolphe Alphand E514303 entity
Predicate givenName P17 FINISHED
Object Adolphe 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: Adolphe | Statement: [Jean-Charles Adolphe Alphand, givenName, Adolphe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Adolphe
Context triple: [Jean-Charles Adolphe Alphand, givenName, Adolphe]
  • A. Adolphe chosen
    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.
  • B. Rodolphe
    Rodolphe is a masculine given name of French origin, historically borne by several notable European artists, writers, and public figures.
  • 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. Gustave
    Gustave is a masculine given name of French origin, famously borne by engineer Gustave Eiffel.
  • E. Hermann von François
    Hermann von François was a German general of World War I, best known for his aggressive leadership of the German Eighth Army corps during the early Eastern Front campaigns, including the battles around Tannenberg and the Masurian Lakes.
  • 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_69e0b4f733f081908a401c0b7beb0b9f completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6d058d4dc81908398f8c75e30dc77 completed April 21, 2026, 1:18 a.m.
Created at: April 16, 2026, 12:46 p.m.