Triple
T37873082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spirit Rise |
E944652
|
entity |
| Predicate | locatedInFranchise |
P102724
|
FINISHED |
| Object | Warcraft |
E932270
|
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: Warcraft | Statement: [Spirit Rise, locatedInFranchise, Warcraft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInFranchise Context triple: [Spirit Rise, locatedInFranchise, Warcraft]
-
A.
includedInFranchise
chosen
Indicates that an entity is part of, or belongs to, a larger franchise or franchise series.
-
B.
usedByFranchise
Indicates that something (such as a resource, asset, or element) is utilized or employed by a particular franchise.
-
C.
partOfFranchiseLineage
Indicates that one entity belongs to, or is derived from, the same overarching franchise lineage as another entity, reflecting continuity within a shared franchise.
-
D.
hasItemInFranchise
Indicates that an entity possesses or includes a specific item as part of a larger franchise or branded collection.
-
E.
followsInFranchise
Indicates that one work or installment comes after another within the same franchise’s internal sequence or continuity.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a4167edb9dc81908ebc36916f840b95 |
completed | June 28, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.