Triple
T37666187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moon Kingdom |
E937823
|
entity |
| Predicate | postGameContent |
P100073
|
FINISHED |
| Object | additional Power Moons after story completion |
—
|
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: additional Power Moons after story completion | Statement: [Moon Kingdom, postGameContent, additional Power Moons after story completion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: postGameContent Context triple: [Moon Kingdom, postGameContent, additional Power Moons after story completion]
-
A.
postGamesUse
Indicates that an entity uses or engages with something after games have concluded.
-
B.
postGamesPlan
Indicates that an entity publishes or shares a plan or strategy related to games after they have concluded.
-
C.
endgameContentFor
chosen
Indicates that something serves as endgame content designed for a particular game, mode, or player progression stage.
-
D.
postGamesDevelopment
Indicates that an entity publishes or shares information about the development progress or updates of games.
-
E.
hasGameContent
Indicates that an entity includes, provides, or is associated with game-related material or features.
- 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_69f76ed6df7c8190b018e5baea716ceb |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba9e16fb881908bb74df86ab04427 |
completed | May 6, 2026, 8:51 p.m. |
| PD | Predicate disambiguation | batch_69fba887821c8190ae93ef1dd389e9c8 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:18 p.m.