Triple

T11738821
Position Surface form Disambiguated ID Type / Status
Subject Battle of Chalgrove Field E279099 entity
Predicate near P350 FINISHED
Object Thame E35624 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: Thame | Statement: [Battle of Chalgrove Field, near, Thame]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Thame
Context triple: [Battle of Chalgrove Field, near, Thame]
  • A. Thame chosen
    Thame is a historic market town in Oxfordshire, England, known for its traditional architecture and vibrant local community.
  • B. Thame
    Thame is a remote Sherpa village in Nepal’s Khumbu region, known as a traditional trading settlement and trekking stop on the route toward the high Himalayas.
  • C. Tshela
    Tshela is a town in the western Democratic Republic of the Congo, situated in the forested interior of Kongo Central Province near the border with the Republic of the Congo.
  • D. Phuthi
    Phuthi is a Bantu language closely related to the Sotho–Tswana group, spoken primarily by the Phuthi people in parts of Lesotho and South Africa.
  • E. Hathawekela
    Hathawekela is a historic division of the Shawnee people, recognized as one of their traditional tribal bands.
  • 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_69d6aaffec6881908bead509e8621742 completed April 8, 2026, 7:22 p.m.
NER Named-entity recognition batch_69d8a4ef1c4881909ad36dc27b1fe193 completed April 10, 2026, 7:21 a.m.
NED1 Entity disambiguation (via context triple) batch_69f019c339cc81909967ecfa234e4ab8 completed April 28, 2026, 2:21 a.m.
Created at: April 8, 2026, 9:41 p.m.