Triple
T33347397
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heroes’ Feast: Flavors of the Multiverse |
E853835
|
entity |
| Predicate | officialLicenseHolder |
P12714
|
FINISHED |
| Object | Wizards of the Coast |
—
|
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: Wizards of the Coast | Statement: [Heroes’ Feast: Flavors of the Multiverse, officialLicenseHolder, Wizards of the Coast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialLicenseHolder Context triple: [Heroes’ Feast: Flavors of the Multiverse, officialLicenseHolder, Wizards of the Coast]
-
A.
hasLicense
chosen
Indicates that an entity possesses a valid authorization or permit, typically granted by an authority, to perform a specific activity or use something.
-
B.
typeOfLicense
Indicates the specific kind or category of license associated with an entity.
-
C.
formerLicensee
Indicates that an entity previously held a license from another entity but no longer does.
-
D.
licenceAuthority
Indicates that one entity has the official power or jurisdiction to grant, issue, or regulate licences for another entity or activity.
-
E.
coLicensedWith
Indicates that two or more entities share a common license or are authorized under the same licensing agreement.
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff6c061c6c81909ff485e9cafc88a2 |
completed | May 9, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ff6aaf886c8190a3c87d089453f3de |
completed | May 9, 2026, 5:11 p.m. |
Created at: May 1, 2026, 1:34 a.m.