Triple
T38464388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papu Papu |
E912526
|
entity |
| Predicate | appearsAsRacerIn |
P84359
|
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, appearsAsRacerIn, Crash Team Racing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsAsRacerIn Context triple: [Papu Papu, appearsAsRacerIn, Crash Team Racing]
-
A.
appearsAsRacerClass
Indicates that an entity is presented or functions in the role or category of a racer class within a given context.
-
B.
appearsInRace
chosen
Indicates that an entity participates as a competitor or entrant in a specific race event.
-
C.
racingDriver
Indicates that one entity is a racing driver, i.e., a person who competes in motor races as a driver.
-
D.
racingModel
Indicates that one entity is a specific model or version designed or configured for racing in relation to another entity.
-
E.
racingSeriesHomologatedFor
Indicates that a racing series has officially approved or certified something (typically a vehicle or component) as eligible to compete in that series.
- 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_69fef2db323c8190821bda53f22a42be |
completed | May 9, 2026, 8:39 a.m. |
| PD | Predicate disambiguation | batch_69fef21d63c88190abf6a99b59b3c655 |
completed | May 9, 2026, 8:36 a.m. |
Created at: May 3, 2026, 4:31 p.m.