Triple
T32732304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Bastard |
E836985
|
entity |
| Predicate | hasCollisionPartner |
—
|
GENERATED |
| Object | 1950 Ford Tudor |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollisionPartner Context triple: [Little Bastard, hasCollisionPartner, 1950 Ford Tudor]
-
A.
collidesParticleType
Indicates that one particle comes into physical contact with and impacts another particle of a specified type.
-
B.
collidesWith
chosen
Indicates that two entities come into contact with each other in space, typically implying an impact or physical intersection of their paths or volumes.
-
C.
colliderUsed
Indicates that a particular collider or collision-detection component is employed or involved in an interaction or event between entities.
-
D.
hasHitbox
Indicates that one entity possesses or is associated with a collision-detection region used to determine physical interactions in a space.
-
E.
marksCollisionBetween
Indicates a recorded event or state where two or more entities have come into contact or collided with each other.
- F. None of above.
Provenance (1 batch)
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_69f34935fb048190ad4967420581f835 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:11 a.m.