Triple
T33457049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Need for Speed III: Hot Pursuit |
E856805
|
entity |
| Predicate | supportsForceFeedback |
P83812
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Need for Speed III: Hot Pursuit, supportsForceFeedback, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsForceFeedback Context triple: [Need for Speed III: Hot Pursuit, supportsForceFeedback, yes]
-
A.
hasRumbleMotors
Indicates that an entity is equipped with rumble (vibration) motors that can provide haptic feedback.
-
B.
supportsVibration
chosen
Indicates that one entity provides the capability or functionality to handle, generate, or respond to vibration for another entity.
-
C.
hasForceStrength
Indicates that one entity possesses a certain level or degree of physical or exerted force strength in relation to another entity or context.
-
D.
supportsForce
Indicates that one entity provides the necessary structure, stability, or resistance to bear, counteract, or transmit a physical force exerted by another entity.
-
E.
isPressureSensitive
Indicates that an entity responds differently based on the amount or intensity of physical pressure applied to it.
- 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_69f3497281a08190b4705de0b5f26ba7 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:37 a.m.