Triple
T28348835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sjösala vals |
E718029
|
entity |
| Predicate | fictionalLocationMentioned |
P84403
|
FINISHED |
| Object | Sjösala |
—
|
NE NERFINISHED |
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: Sjösala | Statement: [Sjösala vals, fictionalLocationMentioned, Sjösala]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalLocationMentioned Context triple: [Sjösala vals, fictionalLocationMentioned, Sjösala]
-
A.
fictionalLocationAssociatedWith
chosen
Indicates a relationship where a fictional entity (such as a character, event, or work) is connected to or set in a particular fictional location.
-
B.
notableFictionalLocationIn
Indicates that a fictional location is notably situated within or strongly associated with a particular larger place or setting.
-
C.
fictionalCountryLocation
Indicates that a fictional country is located within, or geographically associated with, a specified place or region.
-
D.
fictionalPlaceType
Indicates that a place is a fictional location and specifies what type or category of fictional place it is.
-
E.
basedInFictionalLocation
Indicates that an entity’s primary setting, origin, or operations occur in a fictional (non-real) 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_69eff6ec27b481908c8d7b86c47893d9 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f78fd5a6388190bfda4bbb2e222e5b |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2ac3fc819081a45c6841375c8d |
completed | May 3, 2026, 6:04 p.m. |
Created at: April 28, 2026, 12:44 a.m.