Triple
T29682571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bullis |
E750994
|
entity |
| Predicate | associatedWithPositioning |
P105158
|
FINISHED |
| Object | behind rear axle |
—
|
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: behind rear axle | Statement: [Bullis, associatedWithPositioning, behind rear axle]
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 (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_69f0d624d7b08190ba237d226f78d0d9 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 28, 2026, 7:11 p.m.