Triple
T13119525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Leaf |
E311685
|
entity |
| Predicate | itemFunctionInMarioKart |
P61300
|
FINISHED |
| Object | creates Tanooki tail around kart |
—
|
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: creates Tanooki tail around kart | Statement: [Super Leaf, itemFunctionInMarioKart, creates Tanooki tail around kart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: itemFunctionInMarioKart Context triple: [Super Leaf, itemFunctionInMarioKart, creates Tanooki tail around kart]
-
A.
hasFunctionInGames
chosen
Indicates that something serves a specific role, purpose, or function within the context of games.
-
B.
featuresRaceBetween
Indicates that an event or context includes or showcases a competitive race occurring between participants.
-
C.
기능
Indicates that an entity has a particular function, role, or operational capability.
-
D.
featuresItem
Indicates that one entity includes, presents, or highlights another entity as a notable item or component.
-
E.
musicVehicle
Indicates a relationship where a vehicle is associated with or used for playing, broadcasting, or producing music.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98196e69081909111407ee3d9f08e |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98041a3548190a05ddd83dbb660fa |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:06 p.m.