Triple
T31483956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hooktail Castle |
E803223
|
entity |
| Predicate | firstChapterDungeonOf |
P100053
|
FINISHED |
| Object | Paper Mario: The Thousand-Year Door |
E493970
|
NE 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: Paper Mario: The Thousand-Year Door | Statement: [Hooktail Castle, firstChapterDungeonOf, Paper Mario: The Thousand-Year Door]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstChapterDungeonOf Context triple: [Hooktail Castle, firstChapterDungeonOf, Paper Mario: The Thousand-Year Door]
-
A.
firstCorridorOpened
Indicates that the first corridor in a sequence or structure has been opened or made accessible.
-
B.
firstAppearanceChapter
Indicates the chapter in which an entity (such as a character, item, or concept) is first introduced or appears in a work.
-
C.
primaryCharacterChambersOf
Indicates that an entity serves as the main or central character within a specified set of chambers or rooms.
-
D.
hasDungeon
chosen
Indicates that one entity possesses, contains, or includes a dungeon as part of its structure, property, or domain.
-
E.
dungeonType
Indicates the specific category or kind of dungeon associated with an entity or location.
- F. None of above.
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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3538e906648190955ebab34618bda7 |
completed | June 19, 2026, 12:41 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 9:34 p.m.