Triple

T12433795
Position Surface form Disambiguated ID Type / Status
Subject Richard Aldington E297093 entity
Predicate nickname P55 FINISHED
Object Richard E19643 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: Richard | Statement: [Richard Aldington, nickname, Richard]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Richard
Context triple: [Richard Aldington, nickname, Richard]
  • A. Richard chosen
    Richard is a common masculine given name of Germanic origin, widely used in English-speaking countries.
  • B. Edward
    Edward is a masculine given name of English origin, historically associated with kings of England and notable figures such as U.S. Senator Edward M. Kennedy.
  • C. Charles
    Charles is a masculine given name of Germanic origin that has been widely used across Europe and the English-speaking world, borne by numerous historical figures, royalty, and notable individuals.
  • D. Rex Anglorum
    Rex Anglorum is a Latin royal title historically used to denote the "King of the English" in medieval England.
  • E. Stephen, King of England
    Stephen, King of England, was a 12th-century monarch whose contested claim to the throne led to a prolonged civil war known as The Anarchy.
  • 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_69d6ada0640c81908c061d7fb3d47786 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d94d804c2c819082f2f86edcbb50de completed April 10, 2026, 7:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6349d29c481909a37fd386cc06575 completed May 2, 2026, 5:30 p.m.
Created at: April 8, 2026, 9:55 p.m.