Triple

T14543648
Position Surface form Disambiguated ID Type / Status
Subject Preston Campbell E341233 entity
Predicate givenName P17 FINISHED
Object Preston E348091 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: [Preston Campbell, givenName, Preston]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Preston
Context triple: [Preston Campbell, givenName, 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 chosen
    Preston is a masculine given name of English origin that has been used both as a first name and a surname.
  • D. Preston
    Preston is a suburb in Melbourne, Australia, served by its own railway station on the metropolitan train network.
  • E. 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.
  • 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_69d822db9c8481908213ceb39585f792 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb1be5a8081909bf727e28a5bba4a completed April 14, 2026, 9:29 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd7a60f2f88190b08fdf0a3095d0a7 completed May 8, 2026, 5:53 a.m.
Created at: April 10, 2026, 1:22 a.m.