Triple
T30799024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | T-bucket |
E784313
|
entity |
| Predicate | typicalChassis |
P62065
|
FINISHED |
| Object | custom-built frame |
—
|
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: custom-built frame | Statement: [T-bucket, typicalChassis, custom-built frame]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalChassis Context triple: [T-bucket, typicalChassis, custom-built frame]
-
A.
supportsChassisType
Indicates that one entity is compatible with and can be used to support or accommodate a specified chassis type.
-
B.
chassis
Indicates that one entity serves as the structural frame or supporting base (chassis) for another entity.
-
C.
chassisConstruction
chosen
Indicates how the chassis of an object is built or assembled, specifying the construction method or structural design used.
-
D.
chassisFeature
Indicates that a particular feature, component, or characteristic is part of or associated with a chassis.
-
E.
chassisMaterialFeature
Indicates that an entity has a chassis characterized by a specific material-related feature or property.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:42 p.m.