Triple
T38591498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silithus |
E932463
|
entity |
| Predicate | containsEntranceTo |
—
|
GENERATED |
| Object | Ahn'Qiraj |
—
|
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: containsEntranceTo Context triple: [Silithus, containsEntranceTo, Ahn'Qiraj]
-
A.
hasEntranceOn
Indicates that one entity’s entrance or access point is located on or faces a specified side, boundary, or feature of another entity.
-
B.
hasEntrancesIn
chosen
Indicates that an entity has one or more entrances located within or opening into another specified entity or area.
-
C.
hasEntrance
Indicates that one entity possesses or provides an entry point or access way to another entity or space.
-
D.
hasEntranceStructure
Indicates that one entity possesses or is associated with a specific physical structure that serves as its entrance.
-
E.
hasNumberOfEntrances
Indicates the relationship that specifies how many entrances an entity possesses.
- F. None of above.
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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.