Triple
T35386177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toad Houses in Super Mario Bros. 3 |
E1022798
|
entity |
| Predicate | hostedByCharacter |
P174471
|
FINISHED |
| Object | Toad |
—
|
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: Toad | Statement: [Toad Houses in Super Mario Bros. 3, hostedByCharacter, Toad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostedByCharacter Context triple: [Toad Houses in Super Mario Bros. 3, hostedByCharacter, Toad]
-
A.
hostsCharacterInDisguise
Indicates that a host entity accommodates or presents a character who is concealed under a false identity or disguise.
-
B.
isFictionalCharacterHost
chosen
Indicates that one entity serves as the host or presenter in a context involving a fictional character.
-
C.
attendedByFictionalCharacter
Indicates that a fictional character is present at, participates in, or is an attendee of a particular event or gathering.
-
D.
coHostOf
Indicates a relationship where two or more entities jointly host the same event, program, or activity together.
-
E.
hostedByTitle
Indicates that an event, program, or content is hosted by a person or entity identified specifically by their title rather than by name.
- 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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f794f649648190a79d90e6e67fe2dc |
completed | May 3, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.