Triple
T36630661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gilmerton Cove |
E904304
|
entity |
| Predicate | hasTourTheme |
P37147
|
FINISHED |
| Object | mystery and speculation about its origins |
—
|
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: mystery and speculation about its origins | Statement: [Gilmerton Cove, hasTourTheme, mystery and speculation about its origins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTourTheme Context triple: [Gilmerton Cove, hasTourTheme, mystery and speculation about its origins]
-
A.
hasTour
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
-
B.
hasAttractionTheme
chosen
Indicates that something (such as a place, event, or attraction) is characterized by or associated with a particular theme or motif.
-
C.
hasFestivalTheme
Indicates that something is associated with, characterized by, or designed around a particular festival-related theme.
-
D.
hasTourElement
Indicates that something includes or is associated with a specific element or component of a tour.
-
E.
hasThemePark
Indicates that one entity owns, contains, or is associated with a theme park as part of its properties or offerings.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd6a1c1c4881908090053bc359b181 |
completed | May 8, 2026, 4:44 a.m. |
| PD | Predicate disambiguation | batch_69fd696f24d8819091033afacbdaadc5 |
completed | May 8, 2026, 4:41 a.m. |
Created at: May 3, 2026, 4:11 p.m.