Triple
T10020686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | St. Thomas Assembly |
E200601
|
entity |
| Predicate | productLayout |
P91736
|
FINISHED |
| Object | body-on-frame sedans |
—
|
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: body-on-frame sedans | Statement: [St. Thomas Assembly, productLayout, body-on-frame sedans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productLayout Context triple: [St. Thomas Assembly, productLayout, body-on-frame sedans]
-
A.
productForm
Indicates the specific physical or presentation format in which a product is offered or delivered (e.g., tablet, liquid, package type).
-
B.
productStyle
Indicates the stylistic category or design theme that characterizes a product.
-
C.
productFor
Indicates that one entity is intended to be used by, with, or in relation to another entity as its product or offering.
-
D.
productStandard
Indicates that an entity complies with, is governed by, or is defined according to a particular product-related standard or specification.
-
E.
productIncludes
Indicates that a product contains, comprises, or is composed of the specified component, item, or feature.
- F. None of above. chosen
Provenance (4 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_69ca831c45f08190ac1505cc15076608 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd777b208190ad75eac79eec0c2f |
completed | April 2, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69cd4b7cd4208190b2253583ee2f892c |
completed | April 1, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69cd4f8d9b888190b8067bd916dae773 |
completed | April 1, 2026, 5:02 p.m. |
Created at: March 30, 2026, 8:53 p.m.