Triple

T18767441
Position Surface form Disambiguated ID Type / Status
Subject Lindsay family E458927 entity
Predicate familyName P18 FINISHED
Object Lindsay 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: Lindsay | Statement: [Lindsay family, familyName, Lindsay]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Lindsay
Context triple: [Lindsay family, familyName, Lindsay]
  • A. Lindsay chosen
    Lindsay is a surname most notably associated with American poet Vachel Lindsay, a key figure in early 20th-century performance and visionary poetry.
  • B. Lindsay
    Lindsay is a small agricultural city in Tulare County, California, known for its citrus production in the San Joaquin Valley.
  • C. Lindsay
    Lindsay is a feminine given name of English origin, used both as a first name and a surname.
  • D. Lindsay
    Lindsay is an Australian federal electoral division in New South Wales that includes the city of Penrith and surrounding suburbs in Western Sydney.
  • E. Lindsay
    Lindsay is a consumer brand best known for its olives and related Mediterranean-style food products.
  • 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_69d8d395dba0819087568404508590cb completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e58d859c8081909cec3aa64d264885 completed April 20, 2026, 2:20 a.m.
Created at: April 10, 2026, 11:52 a.m.