Triple

T1138871
Position Surface form Disambiguated ID Type / Status
Subject Charles Spencer, 3rd Earl of Sunderland E23402 entity
Predicate familyName P18 FINISHED
Object Spencer E71790 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: Spencer | Statement: [Charles Spencer, 3rd Earl of Sunderland, familyName, Spencer]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Spencer
Context triple: [Charles Spencer, 3rd Earl of Sunderland, familyName, Spencer]
  • A. Spencer chosen
    Spencer is a masculine given name of English origin, historically associated with roles such as steward or dispenser and borne by various notable figures.
  • B. Spencer
    Spencer is the middle name of American author and aviator Anne Spencer Lindbergh, reflecting her family’s naming tradition.
  • C. Spencer Brook
    Spencer Brook is a smaller tributary stream that feeds into New York’s Croton River within the Croton River watershed system.
  • D. Spencer Rivers
    Spencer Rivers is the son of American sportscaster and former NBA player Doc Rivers.
  • E. Parker
    Parker is a common English surname borne by numerous notable individuals across fields such as politics, sports, arts, and science.
  • 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_69a493ef399c8190b04b9146d2314f59 completed March 1, 2026, 7:30 p.m.
NER Named-entity recognition batch_69a4bc25dda481909a26d726fdbdbb50 completed March 1, 2026, 10:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac7f30222081909679902c6e0d4790 completed March 7, 2026, 7:40 p.m.
Created at: March 1, 2026, 7:44 p.m.