Triple
T27747914
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ge 4/4 III |
E702036
|
entity |
| Predicate | hasSpecialLiveries |
P21786
|
FINISHED |
| Object | advertising 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: advertising liveries | Statement: [Ge 4/4 III, hasSpecialLiveries, advertising liveries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpecialLiveries Context triple: [Ge 4/4 III, hasSpecialLiveries, advertising liveries]
-
A.
hasLivery
chosen
Indicates that one entity bears or displays the distinctive colors, markings, or branding (livery) associated with another entity.
-
B.
liveryColors
Indicates the specific set of colors used as the official or characteristic color scheme associated with an entity (such as a brand, organization, or vehicle).
-
C.
liveryFeature
Indicates a characteristic or design element that is part of a specific livery or external appearance scheme.
-
D.
liveryInspiredBy
Indicates that one livery’s design, colors, or overall appearance is based on, influenced by, or pays homage to another livery.
-
E.
liveryNumber
Indicates the identifying number assigned to a vehicle or asset within a particular livery or fleet.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 27, 2026, 4:18 p.m.