Triple

T17874867
Position Surface form Disambiguated ID Type / Status
Subject Ebenezer Allen E446926 entity
Predicate familyName P18 FINISHED
Object Allen 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: Allen | Statement: [Ebenezer Allen, familyName, Allen]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Allen
Context triple: [Ebenezer Allen, familyName, Allen]
  • A. Allen chosen
    Allen is a common English-language surname borne by numerous notable individuals across politics, sports, entertainment, and other fields.
  • B. Allen
    Allen is a city in Argentina’s Alto Valle region, known primarily for its fruit production and agriculture-based economy.
  • C. Allen
    Allen was the French-made leather football used as the official match ball of the 1938 FIFA World Cup.
  • D. Allen
    Allen is a masculine given name of Celtic origin that is widely used in English-speaking countries.
  • E. Allen
    Allen is a suburban city in Collin County, Texas, known for its rapid growth, family-friendly communities, and location within the Dallas–Fort Worth metropolitan area.
  • 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_69d8b9f4c22c819093c2680434472894 completed April 10, 2026, 8:51 a.m.
NER Named-entity recognition batch_69e49aa54d1481908c0af8533edd51c4 completed April 19, 2026, 9:04 a.m.
Created at: April 10, 2026, 10:18 a.m.