Triple
T15384191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Game Boy Horror |
E367876
|
entity |
| Predicate | hasNamePun |
P36401
|
FINISHED |
| Object | horror |
—
|
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: horror | Statement: [Game Boy Horror, hasNamePun, horror]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNamePun Context triple: [Game Boy Horror, hasNamePun, horror]
-
A.
hasRhymingName
Indicates that one entity has a name that rhymes with the name of another entity.
-
B.
hasTitlePun
chosen
Indicates that an entity’s title involves a pun or wordplay, typically combining multiple meanings or sounds for humorous or clever effect.
-
C.
namePunOn
Indicates that one entity’s name is a play on, parody of, or humorous variation of another entity’s name.
-
D.
hasNameInPunjabi
Indicates that an entity is associated with a specific name expressed in the Punjabi language.
-
E.
usesNameDueTo
Indicates that one entity adopts or applies a particular name for another entity specifically because of some motivating reason, circumstance, or dependency.
- 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_69d85a1551a08190ba2caea7cd51c639 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e7397188190bde42b897ab4b5b4 |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27742a881909cd73cc5c7d062fd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.