Triple
T38464530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | N. Tropy |
E912529
|
entity |
| Predicate | appearsAsPlayableCharacterIn |
P43877
|
FINISHED |
| Object | Crash Team Racing |
—
|
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: Crash Team Racing | Statement: [N. Tropy, appearsAsPlayableCharacterIn, Crash Team Racing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsAsPlayableCharacterIn Context triple: [N. Tropy, appearsAsPlayableCharacterIn, Crash Team Racing]
-
A.
hasPlayableCharacter
chosen
Indicates that an entity includes or is associated with a character that a user can control or play as.
-
B.
playsInGame
Indicates that an entity participates as a player in a particular game or match.
-
C.
appearedInVideoGame
Indicates that an entity is featured as a character, element, or content within a specific video game.
-
D.
characterInPlayBy
Indicates that a character appears in or is part of a play authored or created by a specific person.
-
E.
smashBrosRole
Indicates that one entity has a specific role or function related to the Super Smash Bros. game or its competitive context in relation to another entity.
- 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_69f76e861d8c81908559031dc66e3c15 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
Created at: May 3, 2026, 4:31 p.m.