Triple

T10510410
Position Surface form Disambiguated ID Type / Status
Subject Edward Burleson E247896 entity
Predicate familyName P18 FINISHED
Object Burleson E445812 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: Burleson | Statement: [Edward Burleson, familyName, Burleson]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Burleson
Context triple: [Edward Burleson, familyName, Burleson]
  • A. Burleson, Texas chosen
    Burleson, Texas is a growing suburban city in the Dallas–Fort Worth metropolitan area known for its family-friendly neighborhoods and proximity to Fort Worth.
  • B. Corryton
    Corryton is an unincorporated community in northeastern Knox County, Tennessee, situated within the Knoxville metropolitan area.
  • C. Braswell
    Braswell is the codename for an Intel low-power system-on-chip platform designed primarily for entry-level desktops and laptops.
  • D. Summerston
    Summerston is a residential suburb in the north-west of Glasgow, Scotland, known for its housing estates, local amenities, and proximity to open green spaces.
  • E. Seagoville
    Seagoville is a small city in North Texas that functions as a suburban community within the greater Dallas–Fort Worth metropolitan area.
  • 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_69d381c4aa948190942e1d803143fb0e completed April 6, 2026, 9:49 a.m.
NER Named-entity recognition batch_69d509b542088190868531f84deaf9e4 completed April 7, 2026, 1:42 p.m.
NED1 Entity disambiguation (via context triple) batch_69d90de6e9508190a1cdf348ec542dd5 completed April 10, 2026, 2:49 p.m.
Created at: April 6, 2026, 12:27 p.m.