Triple
T37874460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elder Rifts |
E944682
|
entity |
| Predicate | hasGameModeType |
P69305
|
FINISHED |
| Object | PvE |
—
|
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: PvE | Statement: [Elder Rifts, hasGameModeType, PvE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGameModeType Context triple: [Elder Rifts, hasGameModeType, PvE]
-
A.
hasGameType
Indicates that an entity (such as a game or match) is associated with a specific category or type of game.
-
B.
appearsInGameMode
chosen
Indicates that an entity is present, available, or featured within a specified game mode.
-
C.
hasGameSystem
Indicates that an item, product, or context is associated with or supports a particular game system or rules framework.
-
D.
gameModeStatus
Indicates the current state or condition of a game mode, such as whether it is active, available, or in a particular operational phase.
-
E.
hasPlayType
Indicates the type or category of play associated with an event, action, or performance.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:19 p.m.