Triple
T37461374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mire Keeper |
E930924
|
entity |
| Predicate | releaseGameMode |
P193865
|
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: [Mire Keeper, releaseGameMode, Standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releaseGameMode Context triple: [Mire Keeper, releaseGameMode, Standard]
-
A.
releaseAdventure
Indicates the act of making an adventure (such as a game, story, or experience) publicly available or officially launched.
-
B.
releaseContext
Indicates ending or relinquishing a previously established context or state associated with an interaction or process.
-
C.
releaseType
Indicates the kind or category of a release event or version associated with an entity.
-
D.
releaseFrom
Indicates that one entity causes or authorizes another entity to be freed, discharged, or removed from a prior state of confinement, obligation, or restriction.
-
E.
releaseForm
Indicates that one entity formally authorizes the release or disclosure of information, rights, or responsibilities to another entity through a consent or waiver document.
- F. None of above. chosen
Provenance (4 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_69f76ec1a1148190b0a961f188d621b0 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd57ba740c8190bd1d40166fccccb7 |
completed | May 8, 2026, 3:25 a.m. |
| PD | Predicate disambiguation | batch_69fd55ee82b881908a639da3a41b3af6 |
completed | May 8, 2026, 3:18 a.m. |
| PDg | Predicate description generation | batch_69fd57b9cdec81908536c4159e375931 |
completed | May 8, 2026, 3:25 a.m. |
Created at: May 3, 2026, 4:17 p.m.