Triple
T35386199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toad Houses in Super Mario Bros. 3 |
E1022798
|
entity |
| Predicate | playerChoiceCount |
P192674
|
FINISHED |
| Object | typically three chests |
—
|
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: typically three chests | Statement: [Toad Houses in Super Mario Bros. 3, playerChoiceCount, typically three chests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerChoiceCount Context triple: [Toad Houses in Super Mario Bros. 3, playerChoiceCount, typically three chests]
-
A.
playerNumber
Indicates the specific jersey or identification number assigned to a player within a team or game context.
-
B.
numberOfTurns
Indicates the total count of discrete turns or rotations involved in an interaction, process, or motion.
-
C.
movementCount
Indicates the number of times a movement or relocation action has occurred between the related entities.
-
D.
movementNumber
Indicates the specific sequential position of a movement within a larger multi-movement work or performance.
-
E.
gamesPlayed
Indicates the number or set of games that an entity has participated in or completed.
- F. None of above. chosen
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_69f76df28d8c819089f2c5799fe7d079 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd231cab588190ad0953dc8f4af8f2 |
completed | May 7, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69fd1aa3f1c481909fe6e9cab1383551 |
completed | May 7, 2026, 11:05 p.m. |
| PDg | Predicate description generation | batch_69fd231bdd108190900369e07c854e95 |
completed | May 7, 2026, 11:41 p.m. |
Created at: May 3, 2026, 4:03 p.m.