Triple
T36189114
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lofoten Links |
E1046936
|
entity |
| Predicate | playableDuring |
P155675
|
FINISHED |
| Object | midnight sun season |
—
|
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: midnight sun season | Statement: [Lofoten Links, playableDuring, midnight sun season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playableDuring Context triple: [Lofoten Links, playableDuring, midnight sun season]
-
A.
playableWith
Indicates that one entity can be used, engaged, or interacted with together alongside another entity, typically in a compatible or cooperative manner.
-
B.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
-
C.
playableMode
Indicates that a particular mode, configuration, or state can be actively used or played within a system or application.
-
D.
playedWhile
chosen
Indicates that one activity or event occurred concurrently with another, with the second serving as the temporal context during which the first was performed.
-
E.
isPlayOn
Indicates that one entity is a pun, wordplay, or creative variation based on the form or meaning of another entity.
- 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_69f76e3d4fbc81908c159c7beeb4ce00 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b69b333081909cadbed3fcb8ecf5 |
completed | May 3, 2026, 8:56 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c2a5f8819094ad4621d7b97e0c |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:08 p.m.