Triple
T38586342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warcraft Adventures: Lord of the Clans |
E932353
|
entity |
| Predicate | hasCutscenesBy |
P197971
|
FINISHED |
| Object | Animation Magic |
—
|
NE NERFINISHED |
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: Animation Magic | Statement: [Warcraft Adventures: Lord of the Clans, hasCutscenesBy, Animation Magic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCutscenesBy Context triple: [Warcraft Adventures: Lord of the Clans, hasCutscenesBy, Animation Magic]
-
A.
hasCutscenes
Indicates that the subject includes or features one or more non-interactive cinematic sequences (cutscenes).
-
B.
appearsInCutscenes
Indicates that the entity is featured or shown within one or more cutscene sequences.
-
C.
hasCinematicShort
Indicates that an entity is associated with or includes a cinematic short film or short-form cinematic content.
-
D.
hasFightSceneWith
Indicates that two entities participate together in a fight scene or combat sequence.
-
E.
hasOpeningScene
Indicates that a work (such as a film, show, or story) possesses a specific initial scene that begins or introduces its narrative.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69febce5877c8190a5e000ef5331ec88 |
completed | May 9, 2026, 4:49 a.m. |
| PD | Predicate disambiguation | batch_69febad1cd588190abc7686bcb39a371 |
completed | May 9, 2026, 4:40 a.m. |
| PDg | Predicate description generation | batch_69febce420b081908e1c052751a22b1f |
completed | May 9, 2026, 4:49 a.m. |
Created at: May 3, 2026, 4:32 p.m.