Triple
T1929578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SLT |
E40911
|
entity |
| Predicate | typicalExteriorFeatures |
P5084
|
FINISHED |
| Object | enhanced exterior trim |
—
|
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: enhanced exterior trim | Statement: [SLT, typicalExteriorFeatures, enhanced exterior trim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalExteriorFeatures Context triple: [SLT, typicalExteriorFeatures, enhanced exterior trim]
-
A.
exteriorFeature
Indicates a relationship where one entity serves as an external or outward-facing feature, element, or characteristic of another entity.
-
B.
exteriorMaterial
Indicates the material that forms the outer surface or outer construction of an object or structure.
-
C.
roofFeature
Indicates that one entity is a feature, element, or characteristic that is part of or associated with a roof.
-
D.
architectureProperty
Indicates that a specified architectural characteristic or feature is attributed to, or associated with, an entity.
-
E.
typicalFeatures
chosen
Indicates that the related entities are characteristic or commonly occurring features or attributes of something.
- 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_69a8864711648190b07bed24ed76258e |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb266dcb4819090be83556615d0db |
completed | March 7, 2026, 5:06 a.m. |
| PD | Predicate disambiguation | batch_69abafeec6f881909d47acb966683279 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.