Triple
T13074707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludwig von Koopa |
E329541
|
entity |
| Predicate | gameplayTrait |
P54192
|
FINISHED |
| Object | can perform spin jumps |
—
|
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: can perform spin jumps | Statement: [Ludwig von Koopa, gameplayTrait, can perform spin jumps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameplayTrait Context triple: [Ludwig von Koopa, gameplayTrait, can perform spin jumps]
-
A.
gameplayMechanic
Indicates a relationship where one entity functions as a rule, system, or interactive feature that defines how another entity can be played or operated within a game.
-
B.
gameFeatures
Indicates that a game includes or offers a particular element, characteristic, or functionality.
-
C.
featuresGame
Indicates that something (such as a platform, service, or collection) includes or presents a particular game as part of its offerings.
-
D.
typicalGame
Indicates a relationship where one entity is characterized as a standard, representative, or commonly occurring example of a game for the other entity or context.
-
E.
GMTrait
chosen
Indicates a general, often stable characteristic or attribute that an entity possesses.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98117209081908272021013df2222 |
completed | April 10, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9 p.m.