Triple

T5997220
Position Surface form Disambiguated ID Type / Status
Subject Whyteleafe E133500 entity
Predicate hasPostTown P2711 FINISHED
Object Whyteleafe E133500 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: Whyteleafe | Statement: [Whyteleafe, hasPostTown, Whyteleafe]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Whyteleafe
Context triple: [Whyteleafe, hasPostTown, Whyteleafe]
  • A. Whyteleafe chosen
    Whyteleafe is a village in Surrey, England, situated on the North Downs and known for its commuter links into London.
  • B. Yarrowitch
    Yarrowitch is a small rural locality in New South Wales, Australia, known for its agricultural landscape and proximity to national parks and natural attractions.
  • C. Trenzalore
    Trenzalore is a planet in the Doctor Who universe best known as the site of a pivotal, prophesied conflict in the Doctor’s timeline.
  • D. Tappara
    Tappara is a prominent professional ice hockey club from Tampere, Finland, known as one of the most successful and historic teams in the Finnish Liiga.
  • E. Teurnia
    Teurnia was an important ancient Roman city that served as a major administrative and cultural center in the province of Noricum, located in what is now southern Austria.
  • 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_69c00870ddbc81909880fa3864f4f38d completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c04ee274e08190b6478c7ae318ae48 completed March 22, 2026, 8:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69c10876d4d0819083ac7431c8abaedd completed March 23, 2026, 9:31 a.m.
Created at: March 22, 2026, 4:05 p.m.