Triple
T37666165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moon Kingdom |
E937823
|
entity |
| Predicate | finalShowdownWith |
P196469
|
FINISHED |
| Object | Bowser |
—
|
NE NERFINISHED |
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: Bowser | Statement: [Moon Kingdom, finalShowdownWith, Bowser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalShowdownWith Context triple: [Moon Kingdom, finalShowdownWith, Bowser]
-
A.
finalAct
Indicates that an action or event is the last or concluding act in a sequence or process.
-
B.
laterFinale
Indicates that one event, episode, or occurrence serves as a concluding part that happens after another referenced event or finale.
-
C.
finalAppearanceIn
Indicates that an entity makes its last or final appearance within a specified work, episode, or context.
-
D.
finalMeetingWith
chosen
Indicates that one entity has its last or concluding meeting or encounter with another entity.
-
E.
hasFinale
Indicates that one entity serves as the concluding or final part (such as an ending segment, episode, or event) of another entity.
- 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_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
Created at: May 3, 2026, 4:18 p.m.