Triple
T15074231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Djurgårdslinjen |
E379956
|
entity |
| Predicate | servesAttractionArea |
P82
|
FINISHED |
| Object | Djurgården island and nearby attractions |
—
|
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: Djurgården island and nearby attractions | Statement: [Djurgårdslinjen, servesAttractionArea, Djurgården island and nearby attractions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesAttractionArea Context triple: [Djurgårdslinjen, servesAttractionArea, Djurgården island and nearby attractions]
-
A.
servesAttraction
Indicates that one entity functions as or provides a service that supports or enhances the experience of a particular attraction.
-
B.
servesResortArea
Indicates that one entity provides services or operational support to a resort area.
-
C.
areaServed
chosen
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
-
D.
areaServedType
Indicates the type or category of area that is served by an entity or service.
-
E.
isMajorAttractionFor
Indicates that something serves as a primary or highly significant draw or point of interest for a particular audience, group, or location.
- 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_69d85cd7683881908d405c1b5d7b4f7f |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69dff7fa0570819088a97b28173154cd |
completed | April 15, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69deb95a182081908fffc4402b02a394 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:02 a.m.