Triple
T38583904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shadowmoon Valley |
E932302
|
entity |
| Predicate | pvpActivity |
P188216
|
FINISHED |
| Object | world PvP objectives |
—
|
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: world PvP objectives | Statement: [Shadowmoon Valley, pvpActivity, world PvP objectives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pvpActivity Context triple: [Shadowmoon Valley, pvpActivity, world PvP objectives]
-
A.
pvpStatus
Indicates whether an entity is currently able or allowed to engage in player-versus-player (PvP) combat with other entities.
-
B.
playerActivities
Indicates the various actions, events, or engagements that a player participates in within a given context or system.
-
C.
hasPvPObjective
chosen
Indicates that an entity includes or is associated with a player-versus-player (PvP) objective or goal.
-
D.
matchdayActivity
Indicates the specific activity, event, or engagement that takes place in connection with a particular match day.
-
E.
hasInGameActivities
Indicates that an entity includes or offers specific activities or actions that can be performed within a game context.
- 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_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.