Triple
T35450655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leknes Airport |
E1024615
|
entity |
| Predicate | servesNearbyAttractions |
P7126
|
FINISHED |
| Object | Lofoten fishing villages |
—
|
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: Lofoten fishing villages | Statement: [Leknes Airport, servesNearbyAttractions, Lofoten fishing villages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesNearbyAttractions Context triple: [Leknes Airport, servesNearbyAttractions, Lofoten fishing villages]
-
A.
hasAttractionNearby
Indicates that one entity is located close to another entity that serves as an attraction or point of interest.
-
B.
servesAttraction
chosen
Indicates that one entity functions as or provides a service that supports or enhances the experience of a particular attraction.
-
C.
isLocalAttraction
Indicates that something serves as a point of interest or attraction within a specific local area or community.
-
D.
relatedAttraction
Indicates that one attraction is associated with or connected to another attraction in some relevant way.
-
E.
offersAttraction
Indicates that one entity provides or presents an attraction, such as an activity, feature, or point of interest, to another entity or audience.
- 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_69f76df92f108190817222e520e22268 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a00053d8004819097ad9cf6431a20a3 |
completed | May 10, 2026, 4:10 a.m. |
| PD | Predicate disambiguation | batch_6a0004b3a82c81908e2bf9a533a93eb6 |
completed | May 10, 2026, 4:08 a.m. |
Created at: May 3, 2026, 4:04 p.m.