Triple
T5576470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chevrolet Bel Air (top trim) |
E146330
|
entity |
| Predicate | introducedAsTrim |
P64537
|
FINISHED |
| Object | 1950 model year |
—
|
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: 1950 model year | Statement: [Chevrolet Bel Air (top trim), introducedAsTrim, 1950 model year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedAsTrim Context triple: [Chevrolet Bel Air (top trim), introducedAsTrim, 1950 model year]
-
A.
notableTrim
Indicates that an entity has a particularly significant or distinguished trim level or decorative variant compared to standard versions.
-
B.
isTrimOf
Indicates that one entity is a version of another with leading and/or trailing whitespace characters removed.
-
C.
introducedVia
Indicates that one entity was brought to the attention, presence, or awareness of another entity through a specific intermediary, method, or channel.
-
D.
introducedPart
Indicates that one entity has brought another entity into existence, use, or awareness as a component or element of something.
-
E.
engineIntroduced
Indicates that a particular engine was first introduced or brought into use at a specific time or in a specific context.
- 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_69c008ffed108190a084602227af6157 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c020697fbc8190bd084d7896db3ab8 |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b147cc081909237f3f2967d4cb8 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f0684908190ae2d14f0bd2ab892 |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:37 p.m.