Triple
T18908759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Votroci |
E462539
|
entity |
| Predicate | clubColorContext |
P61756
|
FINISHED |
| Object | black and white (FC Hradec Králové colors) |
—
|
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 and white (FC Hradec Králové colors) | Statement: [Votroci, clubColorContext, black and white (FC Hradec Králové colors)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clubColorContext Context triple: [Votroci, clubColorContext, black and white (FC Hradec Králové colors)]
-
A.
teamColorContext
chosen
Indicates the contextual or situational association between a team and its designated color.
-
B.
teamColor
Indicates the association between a team and the color that represents or identifies it.
-
C.
clubColorsDisplayed
Indicates that the colors associated with a club are being visibly shown or presented.
-
D.
clubColorsMeaning
Indicates the symbolic significance or intended message conveyed by a club’s official colors.
-
E.
teamColorsImplied
Indicates that the colors associated with a team are inferred or derived from context rather than explicitly specified.
- 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_69d8dcfd05bc819088903cca13cc2846 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5c52eed1881908929dace845ae008 |
completed | April 20, 2026, 6:18 a.m. |
| PD | Predicate disambiguation | batch_69e4a2e9e6488190ba8df92c8058ed88 |
completed | April 19, 2026, 9:39 a.m. |
Created at: April 10, 2026, 11:58 a.m.