Triple
T30131062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingston Lisle |
E765845
|
entity |
| Predicate | hasNearbyHillFigure |
P120216
|
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: [Kingston Lisle, hasNearbyHillFigure, Uffington White Horse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyHillFigure Context triple: [Kingston Lisle, hasNearbyHillFigure, Uffington White Horse]
-
A.
hasHillFigure
chosen
Indicates that a location or area contains or features a hill figure (a large design or image created on a hillside).
-
B.
hasNearbyArchaeologicalSite
Indicates that an entity is located close to or in the vicinity of an archaeological site.
-
C.
hasNearbyHills
Indicates that one location or area is situated close to one or more hills.
-
D.
hasArchaeologicalMound
Indicates that an entity possesses or contains an archaeological mound, i.e., a raised earthwork or mound of archaeological significance located on or within it.
-
E.
isAssociatedWithHill
Indicates a relationship where an entity is connected or related in some notable way to a hill.
- 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_69f22477d1a081908df2b7e6ed16859d |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: April 29, 2026, 7:15 p.m.