Triple
T35867318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Darkness Falls franchise |
E1037121
|
entity |
| Predicate | primaryMonster |
P4675
|
FINISHED |
| Object | Tooth Fairy |
E137190
|
NE 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: Tooth Fairy | Statement: [Darkness Falls franchise, primaryMonster, Tooth Fairy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryMonster Context triple: [Darkness Falls franchise, primaryMonster, Tooth Fairy]
-
A.
primaryEnemy
chosen
Indicates that one entity is the main or most significant adversary or opponent of another entity.
-
B.
primaryAntagonistSpeciesFaced
Indicates the species that serves as the main opposing or enemy group confronted by a given entity.
-
C.
mainMonsterDescription
Indicates the primary descriptive text that characterizes the main monster in a given context or scenario.
-
D.
featuresMonster
Indicates that something includes or prominently presents a monster as part of its content or composition.
-
E.
primaryAISpecies
Indicates that one species is the main or dominant species associated with a particular AI system or AI-related context.
- F. None of above.
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_69f76e1d279c8190843e5b64a0a12c3f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037ce70f54819082946dad8d380825 |
completed | May 12, 2026, 7:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38b6eb8cb481909b5b3658a3229995 |
completed | June 22, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_6a037a069e6c8190857b611fffb7b867 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:06 p.m.