Triple
T14699206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strange Game |
E345246
|
entity |
| Predicate | firstUsedInEpisodeType |
P91342
|
FINISHED |
| Object | opening credits |
—
|
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: opening credits | Statement: [Strange Game, firstUsedInEpisodeType, opening credits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUsedInEpisodeType Context triple: [Strange Game, firstUsedInEpisodeType, opening credits]
-
A.
firstEpisode
Indicates that one entity is the initial or earliest episode in the series or sequence associated with another entity.
-
B.
appearsInEpisodeType
chosen
Indicates that an entity is featured in, or associated with, a specific type or category of episode.
-
C.
firstAppearanceType
Indicates the type or category of context (e.g., medium, format, or work) in which an entity makes its first recorded appearance.
-
D.
firstAppearanceEpisode
Indicates the specific episode in which an entity (such as a character or item) is shown or mentioned for the first time.
-
E.
firstAppearanceEpisodeNumber
Indicates the episode number in which an entity (such as a character or item) first appears.
- 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_69d822e4a8c08190a155df736bb7bc13 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb604f88081908a677175045496d0 |
completed | April 14, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69de657c57ec8190ae0b9bb79a514566 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.