Triple
T37471568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyrian (language) |
E931165
|
entity |
| Predicate | usedInRealm |
P1248
|
FINISHED |
| Object | Bastion (World of Warcraft) |
—
|
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: Bastion (World of Warcraft) | Statement: [Kyrian (language), usedInRealm, Bastion (World of Warcraft)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInRealm Context triple: [Kyrian (language), usedInRealm, Bastion (World of Warcraft)]
-
A.
residesInRealm
Indicates that an entity lives or exists within a particular realm or domain.
-
B.
usedInDomain
chosen
Indicates that something (such as a concept, method, or resource) is applied or utilized within a particular domain or field.
-
C.
includesRealm
Indicates that one entity encompasses or contains a particular realm as part of its scope or domain.
-
D.
usedInEntity
Indicates that one entity is utilized, applied, or functions as a component within another entity.
-
E.
associatedWithRealm
Indicates a relationship where an entity is linked or connected to a particular realm, domain, or sphere of influence.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff289541e0819096eeceb8e6332650 |
completed | May 9, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69ff281ab1988190920f0443be9f10cc |
completed | May 9, 2026, 12:27 p.m. |
Created at: May 3, 2026, 4:17 p.m.