Triple
T37254036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faxafoss |
E924072
|
entity |
| Predicate | locatedOnTouristRoute |
P201679
|
FINISHED |
| Object | Golden Circle |
E267081
|
NE 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: Golden Circle | Statement: [Faxafoss, locatedOnTouristRoute, Golden Circle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnTouristRoute Context triple: [Faxafoss, locatedOnTouristRoute, Golden Circle]
-
A.
locatedOnTrekkingRoute
Indicates that something is situated along or directly on a designated trekking or hiking route.
-
B.
locatedInTourismCircuit
chosen
Indicates that a place or attraction is part of, or included within, a defined tourism circuit or route.
-
C.
locatedOnRouteTo
Indicates that one entity lies along the path or course taken when traveling from a starting point to a specified destination.
-
D.
situatedOnTransportRoute
Indicates that one entity is located along, on, or directly adjacent to a specified transport route (such as a road, railway, or shipping lane).
-
E.
hasTouristRoute
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
- F. None of above.
Provenance (4 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_69f76eaabb4c819093b751b139dad551 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4043d3bb4c81908b62cff2c9f27271 |
completed | June 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:15 p.m.