Triple
T5870439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steel City derby |
E130501
|
entity |
| Predicate | hasColourAssociation |
P65875
|
FINISHED |
| Object | blue and white (Sheffield Wednesday) |
—
|
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 white (Sheffield Wednesday) | Statement: [Steel City derby, hasColourAssociation, blue and white (Sheffield Wednesday)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasColourAssociation Context triple: [Steel City derby, hasColourAssociation, blue and white (Sheffield Wednesday)]
-
A.
associatedColour
chosen
Indicates that one entity is linked to another as its characteristic or representative colour.
-
B.
colorHasMeaning
Indicates that a particular color is associated with or conveys a specific meaning, symbolism, or significance.
-
C.
colors
Indicates that one entity assigns, describes, or provides the color or colors of another entity.
-
D.
sharesColorsWith
Indicates that two entities have one or more colors in common.
-
E.
notableColor
Indicates that an entity is characteristically or prominently associated with a particular color.
- 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_69c0085047dc8190af24e311edad3c07 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ffaef081909faaa7f420a3b9b7 |
completed | March 22, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69c03347e51c81909053bcf34e3b88ab |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:56 p.m.