Triple
T5252190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alfa Romeo Spider |
E118613
|
entity |
| Predicate | series3Feature |
P19394
|
FINISHED |
| Object | black plastic bumpers |
—
|
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: black plastic bumpers | Statement: [Alfa Romeo Spider, series3Feature, black plastic bumpers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: series3Feature Context triple: [Alfa Romeo Spider, series3Feature, black plastic bumpers]
-
A.
seriesBy
Indicates that one entity is the creator, author, or originator of a series to which the other entity belongs.
-
B.
featuresStar
Indicates that one entity prominently includes or showcases another entity as a main star or featured performer.
-
C.
thirdSeriesCode
Indicates that an entity is associated with a specific code identifying its third series or third-level sequence within a set or classification.
-
D.
specialFeature
chosen
Indicates that an entity possesses a distinctive or noteworthy attribute, capability, or characteristic that sets it apart from others.
-
E.
seriesType
Indicates the classification or category of a series that an entity belongs to or is associated with.
- 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_69bd446978108190bb5f9c5c23d93f88 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7b7b840881908bb1ecb8a0047382 |
completed | March 20, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69bd77c30bac8190a883ca45da35d667 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.