Triple
T27650403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ormiston, East Lothian |
E696836
|
entity |
| Predicate | hasNearbyHistoricFeature |
P87975
|
FINISHED |
| Object | Ormiston Yew |
—
|
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: Ormiston Yew | Statement: [Ormiston, East Lothian, hasNearbyHistoricFeature, Ormiston Yew]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyHistoricFeature Context triple: [Ormiston, East Lothian, hasNearbyHistoricFeature, Ormiston Yew]
-
A.
hasNearbyHistoricArea
Indicates that one entity is located close to another entity that is designated as a historic area.
-
B.
nearbyHistoricalFunction
Indicates that one entity is located close to another entity that has or had a historical role, use, or function.
-
C.
nearbyHistoricalServiceFor
Indicates that a historical service or facility is located close to a given reference entity or location.
-
D.
hasAdjacentHistoricSite
chosen
Indicates that one place is directly next to or very near another place that is recognized as a historic site.
-
E.
hasNearbyHistoricalEvent
Indicates that a given entity is located close to the site where a specific historical event occurred.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
Created at: April 27, 2026, 2:31 p.m.