Triple
T37540376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abathur |
E933310
|
entity |
| Predicate | locationInHotS |
—
|
GENERATED |
| Object | Leviathan |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationInHotS Context triple: [Abathur, locationInHotS, Leviathan]
-
A.
locationScrapped
Indicates that the location associated with an entity has been removed, discarded, or is no longer considered valid or in use.
-
B.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
C.
currentlyLocatedAt
Indicates that an entity’s present or most recent known physical location is at the specified place.
-
D.
locationFound
Indicates that a particular entity is located or discovered at a specific place or position.
-
E.
locationInSystem
Indicates that one entity is situated within or belongs to the spatial or organizational bounds of a particular system.
- F. None of above. chosen
Provenance (1 batch)
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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:17 p.m.