Triple
T37515973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Covenants of the Shadowlands |
E932633
|
entity |
| Predicate | gameSystemScope |
P127054
|
FINISHED |
| Object | max-level content |
—
|
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: max-level content | Statement: [The Covenants of the Shadowlands, gameSystemScope, max-level content]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameSystemScope Context triple: [The Covenants of the Shadowlands, gameSystemScope, max-level content]
-
A.
hasGameSystem
chosen
Indicates that an item, product, or context is associated with or supports a particular game system or rules framework.
-
B.
gameEngineUsage
Indicates that one entity (such as a project or product) uses or is built upon a particular game engine.
-
C.
gameContext
Indicates the situational framework or environment in which a game’s actions, rules, and interactions take place.
-
D.
gameEngine
Indicates that one entity serves as the game engine or core runtime system used to develop, run, or power another entity (such as a game or interactive application).
-
E.
gameModeRule
Indicates a rule or constraint that defines how a particular game mode operates or is played.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.