Triple

T6014472
Position Surface form Disambiguated ID Type / Status
Subject Adolphe Alphand E133913 entity
Predicate hasGivenName P17 FINISHED
Object Adolphe E133913 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: Adolphe | Statement: [Adolphe Alphand, hasGivenName, Adolphe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Adolphe
Context triple: [Adolphe Alphand, hasGivenName, 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. Gustave
    Gustave is a masculine given name of French origin, famously borne by engineer Gustave Eiffel.
  • C. Léopold
    Léopold is a given name of French origin historically used in Europe, including by figures such as the naturalist Georges Cuvier.
  • 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. Ferdinande
    Ferdinande is the given name of Archduchess Auguste Ferdinande of Austria, a 19th-century member of the Habsburg-Lorraine dynasty.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69c0087361a48190905c6b55969852b8 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c04f544fd88190b6777c4db04e274f completed March 22, 2026, 8:21 p.m.
NED1 Entity disambiguation (via context triple) batch_69c1136a4720819092bf2c6a9101c71b completed March 23, 2026, 10:18 a.m.
Created at: March 22, 2026, 4:06 p.m.