Triple

T25493814
Position Surface form Disambiguated ID Type / Status
Subject Uffington, Berkshire, England E638901 entity
Predicate hasNearbyScheduledMonument P115556 FINISHED
Object Uffington White Horse NE NERFINISHED

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: Uffington White Horse | Statement: [Uffington, Berkshire, England, hasNearbyScheduledMonument, Uffington White Horse]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasNearbyScheduledMonument
Context triple: [Uffington, Berkshire, England, hasNearbyScheduledMonument, Uffington White Horse]
  • A. hasScheduledMonument chosen
    Indicates that an entity is associated with, or contains, a site or structure officially designated as a scheduled monument.
  • B. nearbyMonumentDedication
    Indicates that a monument located close to a given reference point has been formally dedicated, typically in honor of a person, event, or concept.
  • C. hasNearbyPilgrimageSite
    Indicates that one entity is located close to a place used as a pilgrimage site for religious or spiritual journeys.
  • D. hasNearbyArchaeologicalSite
    Indicates that an entity is located close to or in the vicinity of an archaeological site.
  • E. nearbyTomb
    Indicates that one entity is located close to or in the immediate vicinity of a tomb.
  • F. None of above.

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_69e75dbbd2a88190b70e1e645de14b9a completed April 21, 2026, 11:21 a.m.
NER Named-entity recognition batch_69f67f0488bc819089fbd2d2478158d3 completed May 2, 2026, 10:47 p.m.
PD Predicate disambiguation batch_69f67e3ed894819094c067c1ef624951 completed May 2, 2026, 10:44 p.m.
Created at: April 21, 2026, 2:39 p.m.