Triple
T38588126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deeprun Tram to Stormwind City |
E932390
|
entity |
| Predicate | mountUsage |
P191947
|
FINISHED |
| Object | mounts allowed |
—
|
LITERAL FINISHED |
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: mounts allowed | Statement: [Deeprun Tram to Stormwind City, mountUsage, mounts allowed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountUsage Context triple: [Deeprun Tram to Stormwind City, mountUsage, mounts allowed]
-
A.
mountUsageAllowed
chosen
Indicates that the use of a mount (e.g., riding or summoning it) is permitted in the given context or situation.
-
B.
spaceUsage
Indicates how much physical or storage space is occupied or utilized by an entity relative to the total available space.
-
C.
mountType
Indicates the manner or configuration in which one object is mounted or attached to another.
-
D.
gridUsage
Indicates how much and in what way an entity consumes or relies on a shared grid-based resource, such as an electrical or data grid.
-
E.
mountsAvailableFrom
Indicates that certain mounts can be obtained or accessed starting from a specified source, location, or provider.
- 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_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
Created at: May 3, 2026, 4:32 p.m.