Triple
T21721565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chevrolet 210 |
E536167
|
entity |
| Predicate | seriesCode |
P145090
|
FINISHED |
| Object | 210 series |
—
|
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: 210 series | Statement: [Chevrolet 210, seriesCode, 210 series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesCode Context triple: [Chevrolet 210, seriesCode, 210 series]
-
A.
thirdSeriesCode
Indicates that an entity is associated with a specific code identifying its third series or third-level sequence within a set or classification.
-
B.
secondSeriesCode
Indicates that one entity is associated with a secondary or follow-up series identified by a specific code.
-
C.
fourthSeriesCode
Indicates that an entity is associated with a specific code identifying its fourth series in an ordered sequence of series.
-
D.
firstSeriesCode
Indicates that an entity is identified as the initial or primary series within a sequence, referenced by a specific code.
-
E.
seriesGeneration
Indicates that one entity is responsible for creating, originating, or giving rise to a series or sequence of related items, events, or works.
- 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_69e0c46c6dd88190a595375fa6ebd701 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd96f1fbc8190a202f834aec1a319 |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:47 p.m.