Triple
T20179498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Budd Company stainless-steel passenger cars |
E492687
|
entity |
| Predicate | typicalExteriorDetail |
P19771
|
FINISHED |
| Object | horizontal fluting |
—
|
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: horizontal fluting | Statement: [Budd Company stainless-steel passenger cars, typicalExteriorDetail, horizontal fluting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalExteriorDetail Context triple: [Budd Company stainless-steel passenger cars, typicalExteriorDetail, horizontal fluting]
-
A.
exteriorFeature
chosen
Indicates a relationship where one entity serves as an external or outward-facing feature, element, or characteristic of another entity.
-
B.
hasExteriorType
Indicates that an entity possesses a specific kind or style of exterior.
-
C.
exteriorShape
Indicates the overall outer form or contour that characterizes how something appears from the outside.
-
D.
exteriorMaterial
Indicates the material that forms the outer surface or outer construction of an object or structure.
-
E.
roofTypeTypical
Indicates that a specified roof type is the common or characteristic roof style typically found for a given context or entity.
- 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_69da6268a034819081cbd9ea5a1c9475 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e668edf27881909820f9103e72533e |
completed | April 20, 2026, 5:57 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:36 p.m.