Triple
T37666032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seaside Kingdom |
E937820
|
entity |
| Predicate | hasPowerMoonCountApprox |
P201078
|
FINISHED |
| Object | over 50 Power Moons including post-game |
—
|
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: over 50 Power Moons including post-game | Statement: [Seaside Kingdom, hasPowerMoonCountApprox, over 50 Power Moons including post-game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPowerMoonCountApprox Context triple: [Seaside Kingdom, hasPowerMoonCountApprox, over 50 Power Moons including post-game]
-
A.
hasPowerMoonsCount
chosen
Indicates that an entity possesses a specified number of Power Moons.
-
B.
hasPowerMoons
Indicates that one entity possesses or contains one or more Power Moons.
-
C.
isOnlyLargeMoonWith
Indicates that one moon is the sole large moon possessing a specified feature, property, or relationship among all moons in consideration.
-
D.
hasMoonWithAtmosphere
Indicates that an object possesses at least one natural satellite (moon) that has an atmosphere.
-
E.
hasApproximateNumberOfKnownMoons
Indicates that an entity is associated with an estimated or non-exact count of moons known to orbit it.
- 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_69ffc7b4c7f88190b6357a44e7f0940f |
completed | May 9, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69ffc755f09c8190995ca00d97336988 |
completed | May 9, 2026, 11:46 p.m. |
Created at: May 3, 2026, 4:18 p.m.