Triple
T11545389
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ashes of Outland |
E273763
|
entity |
| Predicate | gameModeCompatibility |
P69305
|
FINISHED |
| Object | Standard |
—
|
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: Standard | Statement: [Ashes of Outland, gameModeCompatibility, Standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameModeCompatibility Context triple: [Ashes of Outland, gameModeCompatibility, Standard]
-
A.
appearsInGameMode
chosen
Indicates that an entity is present, available, or featured within a specified game mode.
-
B.
primaryGameMode
Indicates the main or default game mode associated with a particular game or gaming context.
-
C.
introducedGameMode
Indicates that an entity caused a particular game mode to be created, revealed, or made available for use.
-
D.
hasCompatibilityMode
Indicates that one entity operates under a special mode or setting designed to maintain compatibility with another entity or with an earlier version.
-
E.
compatibilityModel
Indicates that one entity is defined or evaluated according to a specific compatibility framework, standard, or model in relation to another entity.
- 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886e1d754819089f3b6be3404fa0b |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d8087cbe7c819085680f3d67ccc978 |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:37 p.m.