Triple
T37095503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warcraft II: Beyond the Dark Portal |
E918548
|
entity |
| Predicate | storyContinues |
P35676
|
FINISHED |
| Object | Orcs vs. Humans conflict |
—
|
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: Orcs vs. Humans conflict | Statement: [Warcraft II: Beyond the Dark Portal, storyContinues, Orcs vs. Humans conflict]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storyContinues Context triple: [Warcraft II: Beyond the Dark Portal, storyContinues, Orcs vs. Humans conflict]
-
A.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
-
B.
storyElement
chosen
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
C.
storyTime
Indicates that one entity is narrating or sharing a story with another entity, typically in a designated or scheduled period for storytelling.
-
D.
storyEngine
Indicates that one entity functions as a narrative-generating or plot-controlling mechanism for another entity or set of events.
-
E.
storyFunction
Indicates that one entity serves a particular narrative role or function within the story structure of another entity.
- 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_69f76e9a48bc8190a3947508d8bca408 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:14 p.m.