Triple
T36937384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kino der Toten |
E913654
|
entity |
| Predicate | easterEggSong |
P186755
|
FINISHED |
| Object | 115 |
—
|
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: 115 | Statement: [Kino der Toten, easterEggSong, 115]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: easterEggSong Context triple: [Kino der Toten, easterEggSong, 115]
-
A.
EasterEgg
Indicates a hidden feature, reference, or message intentionally embedded within something for discovery, often as a playful or secret bonus.
-
B.
hasEasterEggsFrom
Indicates that something contains or includes hidden features, messages, or surprises that originate from or are created by a specified source.
-
C.
EasterEggTrigger
Indicates a condition or event that, when met, activates a hidden or secret feature, message, or behavior.
-
D.
appearsInSongBy
Indicates that an entity is mentioned, referenced, or featured within a song created or performed by a specified artist or musical act.
-
E.
lyricsOfThemeSongBy
Indicates that one entity is the creator or performer of the theme song whose lyrics are associated with another entity.
- F. None of above. chosen
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_69f76e8a6a5c81909c1febf32bf3fe23 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fa0a799b9081909bfa8293a22c4b00 |
completed | May 5, 2026, 3:19 p.m. |
Created at: May 3, 2026, 4:13 p.m.