Triple
T29682573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bullis |
E750994
|
entity |
| Predicate | associatedWithBodyConstruction |
P23419
|
FINISHED |
| Object | boxy shape |
—
|
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: boxy shape | Statement: [Bullis, associatedWithBodyConstruction, boxy shape]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithBodyConstruction Context triple: [Bullis, associatedWithBodyConstruction, boxy shape]
-
A.
associatedWithBodyStyles
chosen
Indicates a relationship where something (such as a product, model, or item) is linked or connected to one or more specific body styles.
-
B.
associatedBody
Indicates a relationship where one entity is linked or connected to another entity as its related or corresponding body.
-
C.
belongsToBody
Indicates that something is a part of, or under the ownership/authority of, a particular body or organization.
-
D.
associatedWithVehicleOrStructure
Indicates that an entity has a relevant connection or involvement with a particular vehicle or structure.
-
E.
associatedWithEngine
Indicates a relationship in which something is connected, linked, or related to an engine, typically through use, function, or dependency.
- 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.