Triple
T5501904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rail Blue |
E144347
|
entity |
| Predicate | followedColourPolicy |
P47061
|
FINISHED |
| Object | standardisation of BR liveries |
—
|
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: standardisation of BR liveries | Statement: [Rail Blue, followedColourPolicy, standardisation of BR liveries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followedColourPolicy Context triple: [Rail Blue, followedColourPolicy, standardisation of BR liveries]
-
A.
hasColourScheme
Indicates that an entity is associated with a particular set or pattern of colors used in its design or appearance.
-
B.
followsTheme
chosen
Indicates that one entity adheres to, is guided by, or is structured according to the theme established by another entity.
-
C.
followsPolityOf
Indicates that one entity adopts, adheres to, or operates under the political system, governance model, or policy framework established by another entity.
-
D.
followsInTheme
Indicates that one element continues or succeeds another while maintaining the same theme or thematic context.
-
E.
capeColor
Indicates the color attribute associated with a cape worn or possessed by an 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_69c008f5a2748190bce7a39aabf87a6d |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f0a512c81908f077378917e5879 |
completed | March 22, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69c01b052f3c81909f71c6add0f35a6f |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:32 p.m.