Triple

T9518795
Position Surface form Disambiguated ID Type / Status
Subject Jervis Pendleton III E229592 entity
Predicate givenName P17 FINISHED
Object Jervis E211834 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: Jervis | Statement: [Jervis Pendleton III, givenName, Jervis]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jervis
Context triple: [Jervis Pendleton III, givenName, Jervis]
  • A. Jervis chosen
    Jervis is a masculine given name of English origin, historically used in various English-speaking countries.
  • B. Nelson
    Nelson is a masculine given name of English origin that has been borne by various notable figures in politics, sports, and the arts.
  • C. Nelson
    Nelson is a common English-language surname borne by numerous notable figures across politics, sports, entertainment, and academia.
  • D. Nelson
    Nelson is a former mill town in Lancashire, England, known for its industrial heritage and location near the Pennine hills.
  • E. Nelson
    Nelson is a coastal city at the top of New Zealand’s South Island, known for its arts scene, sunny climate, and access to nearby national parks.
  • 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_69ca847870a881909d8d751a7d29da39 completed March 30, 2026, 2:11 p.m.
NER Named-entity recognition batch_69cd9881e0f081909a0177cedc2e8b95 completed April 1, 2026, 10:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69d13a51292c8190b871509a32897251 completed April 4, 2026, 4:20 p.m.
Created at: March 30, 2026, 7:59 p.m.