Triple

T4627060
Position Surface form Disambiguated ID Type / Status
Subject Leuchars E101123 entity
Predicate isNear P350 FINISHED
Object Guardbridge E317409 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: Guardbridge | Statement: [Leuchars, isNear, Guardbridge]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Guardbridge
Context triple: [Leuchars, isNear, Guardbridge]
  • A. Guardbridge chosen
    Guardbridge is a small Scottish village in Fife, situated near the River Eden and known historically for its paper mill and as a gateway to St Andrews.
  • B. Havelock
    Havelock is an English surname most notably associated with Sir Henry Havelock, a 19th-century British general known for his role in the Indian Rebellion of 1857.
  • C. Humphreys
    Humphreys is a small unincorporated community located within Lea County in southeastern New Mexico.
  • D. Bulwark
    Bulwark is a residential suburb located on the outskirts of the town of Chepstow in Monmouthshire, Wales.
  • E. Everard
    Everard is a masculine given name of Old English origin, historically meaning “brave boar” or “strong as a wild boar.”
  • 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_69bd43d0497c8190ac23c65c5804846a completed March 20, 2026, 12:55 p.m.
NER Named-entity recognition batch_69bd5a0a7b588190bc6552ee5babb198 completed March 20, 2026, 2:30 p.m.
NED1 Entity disambiguation (via context triple) batch_69bdfaafa6108190bad95e2a7e5a2ff8 completed March 21, 2026, 1:55 a.m.
Created at: March 20, 2026, 1:13 p.m.