Triple

T20308521
Position Surface form Disambiguated ID Type / Status
Subject Nicolson E510167 entity
Predicate relatedToSurname P49952 FINISHED
Object Nicholl 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: Nicholl | Statement: [Nicolson, relatedToSurname, Nicholl]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nicholl
Context triple: [Nicolson, relatedToSurname, Nicholl]
  • A. Nicholl chosen
    Nicholl is a surname of British origin, often considered a variant of the name Nicol or Nicholas.
  • B. Challis
    Challis is an English surname borne by various notable individuals across fields such as cinematography, science, and public service.
  • C. Colehill
    Colehill is a residential parish and suburb in Dorset, England, situated on the outskirts of the Poole–Bournemouth urban area.
  • D. Nicolls
    Nicolls is an English surname historically associated with figures such as Richard Nicolls, the first English colonial governor of New York.
  • E. Naville
    Naville is a Swiss surname most notably associated with Édouard Naville, a prominent 19th–20th century Egyptologist and biblical scholar.
  • 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_69e0b4c7491c8190961113c4283b10b0 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e677411cf08190ba7e98a4135b643a completed April 20, 2026, 6:58 p.m.
Created at: April 16, 2026, 11:18 a.m.