Triple
T33295652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jak X: Combat Racing |
E852436
|
entity |
| Predicate | hasPowerUpType |
P175246
|
FINISHED |
| Object | offensive power-ups |
—
|
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: offensive power-ups | Statement: [Jak X: Combat Racing, hasPowerUpType, offensive power-ups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPowerUpType Context triple: [Jak X: Combat Racing, hasPowerUpType, offensive power-ups]
-
A.
hasPowerUpItem
Indicates that an entity possesses or is currently benefiting from a power-up item.
-
B.
powerUpSystemType
chosen
Indicates the type or method by which a system is powered up or activated.
-
C.
hadPowerType
Indicates that an entity possessed or was associated with a specific type or category of power.
-
D.
hasAssociatedPower
Indicates that one entity possesses, is linked to, or is characterized by a particular power or capability.
-
E.
hasPower
Indicates that one entity possesses authority, control, or influence over another entity or over a particular domain or resource.
- 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_69f34966ed4c81908dc9dda82d8c7fe3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fee25dbca481909e6f1c255122b3a8 |
completed | May 9, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69fee1c8915c8190b08b63e42881f1a9 |
completed | May 9, 2026, 7:27 a.m. |
Created at: May 1, 2026, 1:33 a.m.