Triple
T8154492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Leyland Mini 1000 |
E190411
|
entity |
| Predicate | notableColorInMedia |
P37838
|
FINISHED |
| Object | citron yellow |
—
|
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: citron yellow | Statement: [British Leyland Mini 1000, notableColorInMedia, citron yellow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableColorInMedia Context triple: [British Leyland Mini 1000, notableColorInMedia, citron yellow]
-
A.
notableColor
chosen
Indicates that an entity is characteristically or prominently associated with a particular color.
-
B.
notableCultImage
Indicates that an entity is associated with a significant or historically important religious or cultic image.
-
C.
notableMedia
Indicates a relationship where a media work is recognized as significant, prominent, or especially relevant in connection with a given entity.
-
D.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
E.
notableUse
Indicates that something is prominently or famously used by a particular entity, context, or for a specific purpose.
- 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_69ca82bfeb6481909d07b91b5cf69f59 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb44d566b08190a6bb672f9c368806 |
completed | March 31, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69cb36a0847c8190af9038aef78319b3 |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:37 p.m.