Triple
T37465721
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Year of the Gryphon |
E931028
|
entity |
| Predicate | includesSet |
P11236
|
FINISHED |
| Object | Forged in the Barrens |
E274204
|
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: Forged in the Barrens | Statement: [Year of the Gryphon, includesSet, Forged in the Barrens]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesSet Context triple: [Year of the Gryphon, includesSet, Forged in the Barrens]
-
A.
areSupersetOf
Indicates that one set contains all elements of another set, possibly along with additional elements.
-
B.
hasSubset
Indicates that one set is entirely contained within another set, with all elements of the first set also belonging to the second.
-
C.
canonicalSetIncludes
Indicates that a canonical or standard set contains the referenced element as one of its members.
-
D.
includesElement
chosen
Indicates that one collection, set, or structure contains a specified element as a member or component.
-
E.
containsTestSet
Indicates that one entity includes or encompasses a particular test set as part of its contents or structure.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a409ef570d08190a937a23dab2b04b1 |
completed | June 28, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_6a037a13a1308190a202df66f4781855 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.