Triple

T16064389
Position Surface form Disambiguated ID Type / Status
Subject Charles Kaznyk E389694 entity
Predicate friend P8712 FINISHED
Object Preston unclear NED1 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: Preston | Statement: [Charles Kaznyk, friend, Preston]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Preston
Context triple: [Charles Kaznyk, friend, Preston]
  • A. Preston
    Preston is a historic industrial city in Lancashire, England, known for its role in the Industrial Revolution and its status as a major urban center in the North West.
  • B. Preston
    Preston is a locality within the Dover District of Kent, England, known as a small rural village community.
  • C. Preston
    Preston is a suburb in Melbourne, Australia, served by its own railway station on the metropolitan train network.
  • D. Preston
    Preston is a village in East Lothian, Scotland, known historically for its association with the nearby town of Prestonpans and its role in the region’s agricultural and industrial development.
  • E. Preston
    Preston is a masculine given name of English origin that has been used both as a first name and a surname.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide. chosen

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_69d86daf32ec8190a8c0466c8f49c3c0 completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e1837b048881908326739bbede756f completed April 17, 2026, 12:48 a.m.
NED1 Entity disambiguation (via context triple) batch_69ffe47ef6648190bf1fe216e78ef660 completed May 10, 2026, 1:50 a.m.
Created at: April 10, 2026, 4:57 a.m.