Triple
T14685700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intercity V set |
E344901
|
entity |
| Predicate | operatorColourScheme |
P29272
|
FINISHED |
| Object | blue and 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: blue and yellow | Statement: [Intercity V set, operatorColourScheme, blue and yellow]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorColourScheme Context triple: [Intercity V set, operatorColourScheme, blue and yellow]
-
A.
hasColourScheme
chosen
Indicates that an entity is associated with a particular set or pattern of colors used in its design or appearance.
-
B.
formerColorScheme
Indicates that an entity previously used a particular color scheme but no longer does so.
-
C.
colorSystem
Indicates that one entity is a system or scheme used to define, organize, or represent the colors of another entity.
-
D.
shellColorVariant
Indicates a specific variation or type of shell color associated with an entity.
-
E.
colors
Indicates that one entity assigns, describes, or provides the color or colors of another entity.
- 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_69d822e34b348190ada4d1cdb6c7c226 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb56bdb8081909ff86440ba20fb1f |
completed | April 14, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69de6579fb7881909becc8f5822b39d4 |
completed | April 14, 2026, 4:04 p.m. |
Created at: April 10, 2026, 1:28 a.m.