Triple

T17926274
Position Surface form Disambiguated ID Type / Status
Subject Charles Reade E448201 entity
Predicate familyName P18 FINISHED
Object Reade 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: Reade | Statement: [Charles Reade, familyName, Reade]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Reade
Context triple: [Charles Reade, familyName, Reade]
  • A. Reade chosen
    Reade is a surname and given name of English origin, historically associated with various notable figures in literature, politics, and public life.
  • B. Reidy
    Reidy is the surname of Affonso Eduardo Reidy, a prominent Brazilian modernist architect known for influential public housing and cultural projects in Rio de Janeiro.
  • C. Morrel
    Morrel is a French surname most notably associated with characters in Alexandre Dumas’ novel "The Count of Monte Cristo."
  • D. Nathaniel
    Nathaniel is a masculine given name of Hebrew origin meaning "gift of God," historically borne by various notable figures in literature, science, and religion.
  • E. Rinehart
    Rinehart is a small unincorporated community located in the U.S. state of Missouri.
  • 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_69d8b9f79d14819095540856928f0e25 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e4a54e03588190b36a9bb88e4085de completed April 19, 2026, 9:50 a.m.
Created at: April 10, 2026, 10:20 a.m.