Triple
T29682571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bullis |
E750994
|
entity |
| Predicate | associatedWithPositioning |
—
|
GENERATED |
| Object | behind rear axle |
—
|
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: associatedWithPositioning Context triple: [Bullis, associatedWithPositioning, behind rear axle]
-
A.
hasPositioning
Indicates that one entity occupies, is arranged in, or is assigned a specific spatial or relative position with respect to another entity or reference frame.
-
B.
associatedWithPositionHolderName
Indicates that an entity is linked to the name of the person or role currently holding a specific position.
-
C.
relativePositioning
chosen
Indicates how one entity is spatially arranged or located in relation to another entity.
-
D.
positionAssociatedWith
Indicates a relationship where a specific role, job, or position is linked or connected to a particular entity, context, or resource.
-
E.
requiresPositioning
Indicates that one entity must be placed or arranged in a specific position or orientation relative to another entity or context for the relationship or action to be valid.
- 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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
Created at: April 28, 2026, 7:11 p.m.