Triple
T464493
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tesla Model 3 |
E8414
|
entity |
| Predicate | interiorFeature |
P6655
|
FINISHED |
| Object | 15-inch central touchscreen (approximate size) |
—
|
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: 15-inch central touchscreen (approximate size) | Statement: [Tesla Model 3, interiorFeature, 15-inch central touchscreen (approximate size)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interiorFeature Context triple: [Tesla Model 3, interiorFeature, 15-inch central touchscreen (approximate size)]
-
A.
hasInteriorFeature
chosen
Indicates that an entity contains or includes a specific feature within its interior space.
-
B.
interiorStyle
Indicates that one entity has a particular interior design style or aesthetic characterized by the other entity.
-
C.
roofFeature
Indicates that one entity is a feature, element, or characteristic that is part of or associated with a roof.
-
D.
furnishingType
Indicates the type or category of furnishings associated with an entity, such as a property or room.
-
E.
withinFeature
Indicates that one entity is spatially contained inside or lies entirely within the bounds of another feature.
- 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_69a2e7f3aeb48190a19453e3a043f486 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2efd5b6b48190ae23968135cf6417 |
completed | Feb. 28, 2026, 1:38 p.m. |
| PD | Predicate disambiguation | batch_69a2edea1acc81908a72d9f4c43438ea |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.