Triple
T26085832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wellow, Hampshire |
E657976
|
entity |
| Predicate | hasNotablePlaceNearby |
P19575
|
FINISHED |
| Object | Embley Park |
—
|
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: Embley Park | Statement: [Wellow, Hampshire, hasNotablePlaceNearby, Embley Park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotablePlaceNearby Context triple: [Wellow, Hampshire, hasNotablePlaceNearby, Embley Park]
-
A.
hasAttractionNearby
Indicates that one entity is located close to another entity that serves as an attraction or point of interest.
-
B.
containsNotablePlace
Indicates that one location includes within its boundaries a place that is considered notable or significant.
-
C.
notableNearbySite
chosen
Indicates that one entity is a significant or noteworthy site located close to another entity.
-
D.
typicalNearbyLandmarks
Indicates that certain landmarks are commonly found in the vicinity of a given place or location.
-
E.
hasRecreationalActivityNearby
Indicates that a location has one or more recreational activities or facilities available in its nearby surroundings.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: April 26, 2026, 7:42 p.m.