Triple
T21531958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maracanazo |
E531250
|
entity |
| Predicate | BrazilSubsequentKitColor |
P117250
|
FINISHED |
| Object | yellow shirt with blue shorts |
—
|
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: yellow shirt with blue shorts | Statement: [Maracanazo, BrazilSubsequentKitColor, yellow shirt with blue shorts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BrazilSubsequentKitColor Context triple: [Maracanazo, BrazilSubsequentKitColor, yellow shirt with blue shorts]
-
A.
inspiredByClubColorsOf
Indicates that something derives its design, appearance, or theme from the colors associated with a particular club.
-
B.
traditionalKitColor
Indicates the customary or historically established color scheme used for an entity’s standard or primary kit or uniform.
-
C.
describesKitColor
chosen
Indicates that an entity specifies or provides information about the color of a kit.
-
D.
clubColorsSecondary
Indicates the secondary or alternate set of colors associated with a club, typically used alongside its primary colors.
-
E.
bandColor
Indicates the color associated with a band, such as a stripe, ring, or marking on an object.
- 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_69e0c45e5b8881908ac18fc2f493b114 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee9d0a0e7c8190bbb7ed5c4dfe33af |
completed | April 26, 2026, 11:17 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:27 p.m.