Triple
T37470454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Covenant Sanctum |
E931138
|
entity |
| Predicate | gameSystemType |
P127054
|
FINISHED |
| Object | endgame progression system |
—
|
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: endgame progression system | Statement: [Covenant Sanctum, gameSystemType, endgame progression system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameSystemType Context triple: [Covenant Sanctum, gameSystemType, endgame progression system]
-
A.
gameEngineType
Indicates the type or category of game engine associated with or used by an entity.
-
B.
hasGameSystem
chosen
Indicates that an item, product, or context is associated with or supports a particular game system or rules framework.
-
C.
hasGameType
Indicates that an entity (such as a game or match) is associated with a specific category or type of game.
-
D.
gameZoneType
Indicates the classification or category of a game zone within a game environment (e.g., safe area, combat zone, tutorial area).
-
E.
gearSystemType
Indicates the specific configuration or category of gear mechanism used in a system or device.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8e61d5a48190afc273af1fb54af9 |
completed | May 6, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0c53c08190b64291bac58cdb4c |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.