Triple
T38585489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tanaan Jungle |
E932335
|
entity |
| Predicate | mountsAvailableFrom |
P191866
|
FINISHED |
| Object | Felsteel Annihilator (via Hellfire Citadel) |
—
|
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: Felsteel Annihilator (via Hellfire Citadel) | Statement: [Tanaan Jungle, mountsAvailableFrom, Felsteel Annihilator (via Hellfire Citadel)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountsAvailableFrom Context triple: [Tanaan Jungle, mountsAvailableFrom, Felsteel Annihilator (via Hellfire Citadel)]
-
A.
mountingLocation
Indicates the physical position or surface on which something is attached, fixed, or installed.
-
B.
mountableBy
Indicates that one entity can be physically mounted, ridden, or climbed upon by another entity.
-
C.
mountableIn
Indicates that one entity can be mounted, installed, or attached within or onto another entity.
-
D.
mountOf
Indicates that one entity serves as the mount or riding animal/creature used by another entity.
-
E.
mappingAvailableTo
Indicates that a mapping or correspondence exists and is accessible between one entity and another.
- F. None of above. chosen
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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
| PDg | Predicate description generation | batch_69fcec5e560481909cd710b88897e833 |
completed | May 7, 2026, 7:47 p.m. |
Created at: May 3, 2026, 4:32 p.m.