Triple
T38464390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papu Papu |
E912526
|
entity |
| Predicate | unlockableCharacterIn |
P35546
|
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: [Papu Papu, unlockableCharacterIn, Crash Team Racing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unlockableCharacterIn Context triple: [Papu Papu, unlockableCharacterIn, Crash Team Racing]
-
A.
unlockable
Indicates that an entity can be opened or made accessible, typically by using a key, code, or other authorized method.
-
B.
unseenCharacter
Indicates that a character exists in the narrative or context but does not appear directly or visibly in the current scene or depiction.
-
C.
hasEnigmaticCharacter
Indicates that something possesses a mysterious, puzzling, or difficult-to-interpret quality or nature.
-
D.
isRecruitableCharacter
chosen
Indicates that a character can be obtained and added to the player’s controllable roster or party.
-
E.
usedByCharacter
Indicates that something (such as an item, ability, or resource) is utilized or employed by a particular character.
- 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_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:31 p.m.