Triple
T11642401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crash Bandicoot 2: Cortex Strikes Back |
E276688
|
entity |
| Predicate | introducedAbility |
P80871
|
FINISHED |
| Object | slide attack |
—
|
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: slide attack | Statement: [Crash Bandicoot 2: Cortex Strikes Back, introducedAbility, slide attack]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAbility Context triple: [Crash Bandicoot 2: Cortex Strikes Back, introducedAbility, slide attack]
-
A.
featuresAbility
Indicates that one entity possesses, includes, or provides a particular ability or capability associated with another entity.
-
B.
introducedFeatureCategory
chosen
Indicates that an entity caused a particular feature category to be created, presented, or made available for the first time.
-
C.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
-
D.
developedCapability
Indicates that an entity has created, acquired, or brought into existence a particular capability through its actions or processes.
-
E.
associatedCapability
Indicates that one entity has a related ability, function, or competence that is linked to or relevant for 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a260ab488190ab1c00d9850f3096 |
completed | April 10, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69d85dd94bdc819091fa2ed33eb31624 |
completed | April 10, 2026, 2:18 a.m. |
Created at: April 8, 2026, 9:39 p.m.