Triple
T36937385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kino der Toten |
E913654
|
entity |
| Predicate | easterEggSongTrigger |
P135945
|
FINISHED |
| Object | three meteor fragments |
—
|
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: three meteor fragments | Statement: [Kino der Toten, easterEggSongTrigger, three meteor fragments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: easterEggSongTrigger Context triple: [Kino der Toten, easterEggSongTrigger, three meteor fragments]
-
A.
easterEggSong
Indicates a hidden or secret song that is revealed only through special actions, conditions, or discoveries.
-
B.
EasterEggTrigger
chosen
Indicates a condition or event that, when met, activates a hidden or secret feature, message, or behavior.
-
C.
EasterEgg
Indicates a hidden feature, reference, or message intentionally embedded within something for discovery, often as a playful or secret bonus.
-
D.
hasEasterEggsFrom
Indicates that something contains or includes hidden features, messages, or surprises that originate from or are created by a specified source.
-
E.
appearsInSongBy
Indicates that an entity is mentioned, referenced, or featured within a song created or performed by a specified artist or musical act.
- 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_69f76e8a6a5c81909c1febf32bf3fe23 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:13 p.m.