Triple
T38592002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anubisath |
E932474
|
entity |
| Predicate | introducedWithContent |
P126484
|
FINISHED |
| Object | Gates of Ahn'Qiraj |
—
|
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: Gates of Ahn'Qiraj | Statement: [Anubisath, introducedWithContent, Gates of Ahn'Qiraj]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedWithContent Context triple: [Anubisath, introducedWithContent, Gates of Ahn'Qiraj]
-
A.
presentedContent
Indicates that one entity has delivered, shown, or made specific content available to another entity or audience.
-
B.
introduced
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
C.
contentIs
chosen
Indicates that one entity serves as, or is equivalent to, the content contained within another entity.
-
D.
introducedAlongWith
Indicates that one entity was introduced or presented at the same time as another entity, as part of a joint or concurrent introduction.
-
E.
coIntroduced
Indicates that two or more entities jointly introduced or presented something together for the first time.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff3fb2318c81908a46c2f513608935 |
completed | May 9, 2026, 2:07 p.m. |
| PD | Predicate disambiguation | batch_69ff3e96dcc48190819f6204680d84aa |
completed | May 9, 2026, 2:03 p.m. |
Created at: May 3, 2026, 4:32 p.m.