Triple
T37897184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mogu'shan Palace |
E945311
|
entity |
| Predicate | timewalkingAvailability |
P13910
|
FINISHED |
| Object | Mists of Pandaria Timewalking |
—
|
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: Mists of Pandaria Timewalking | Statement: [Mogu'shan Palace, timewalkingAvailability, Mists of Pandaria Timewalking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timewalkingAvailability Context triple: [Mogu'shan Palace, timewalkingAvailability, Mists of Pandaria Timewalking]
-
A.
hasApproximateWalkingTimeTo
Indicates that there is an estimated or approximate amount of time it takes to walk from one entity to another.
-
B.
availableWith
chosen
Indicates that one entity can be obtained, accessed, or used in conjunction with another entity.
-
C.
kitAvailability
Indicates that a particular kit is available for use, access, or distribution in a given context.
-
D.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
E.
availabilityModel
Indicates how and under what conditions an entity is available for use, access, or interaction.
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:19 p.m.