Triple

T7250525
Position Surface form Disambiguated ID Type / Status
Subject Matthew Edward Lowe E157586 entity
Predicate familyName P18 FINISHED
Object Lowe E295304 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: Lowe | Statement: [Matthew Edward Lowe, familyName, Lowe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lowe
Context triple: [Matthew Edward Lowe, familyName, Lowe]
  • A. Lowe chosen
    Lowe is a common English surname of Anglo-Saxon origin, often derived from the Old English word for a small hill or burial mound.
  • B. Talbot
    Talbot is a surname of English and Norman origin, historically associated with several notable families and individuals.
  • C. Barlow
    Barlow is a surname most notably associated with John Perry Barlow, the American poet, essayist, and co-founder of the Electronic Frontier Foundation.
  • D. Spottiswoode
    Spottiswoode is a surname most notably associated with British-Canadian film director Roger Spottiswoode.
  • E. Louw
    Louw is a surname of Afrikaans and Dutch origin borne by several notable South African figures, including writers and public personalities.
  • 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_69c6882d81d4819085f7ff862951ee4f completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6ea791fec8190aee56ab4503770be completed March 27, 2026, 8:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7d3a2ba748190890c2980ca4a8ecd completed March 28, 2026, 1:12 p.m.
Created at: March 27, 2026, 2:56 p.m.