Triple
T21153246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Machrie |
E521245
|
entity |
| Predicate | hasNearbyView |
P127904
|
FINISHED |
| Object | views over Machrie Bay |
—
|
LITERAL 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: views over Machrie Bay | Statement: [Machrie, hasNearbyView, views over Machrie Bay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyView Context triple: [Machrie, hasNearbyView, views over Machrie Bay]
-
A.
hasViewingPointFor
chosen
Indicates that one entity serves as a vantage point or location from which another entity can be viewed or observed.
-
B.
hasNearbyMode
Indicates that one entity has another entity located close enough to be considered in its immediate vicinity or surrounding area.
-
C.
hasNearbyCove
Indicates that one location is situated close to a small sheltered bay or cove.
-
D.
hasNearbyFunction
Indicates that one entity has another entity located close by that serves a related or supportive function.
-
E.
hasNotableNearbyEntity
Indicates that one entity has another significant or noteworthy entity located in its close physical or contextual proximity.
- 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_69e0b50d1ea481909c07e63c3ead9316 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7252929748190afd85be40294293f |
completed | April 21, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f5f8a5bc819081918c7fa8e4496d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:58 p.m.