Triple
T11412422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Checkerboard Division |
E270403
|
entity |
| Predicate | hasInsigniaColors |
P57860
|
FINISHED |
| Object | black |
—
|
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 | Statement: [Checkerboard Division, hasInsigniaColors, black]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInsigniaColors Context triple: [Checkerboard Division, hasInsigniaColors, black]
-
A.
hasInsigniaComponent
Indicates that an entity includes, bears, or is composed of a particular insignia or emblem as one of its components.
-
B.
hasEmblemColor
chosen
Indicates that an emblem possesses or is characterized by a specific color.
-
C.
usesBrandColor
Indicates that one entity applies or displays another entity’s official brand color in its appearance, design, or materials.
-
D.
insigniaColorContext
Indicates the contextual circumstances or conditions under which a particular insignia color is used or holds its specific meaning.
-
E.
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).
- 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_69d6aaddeaa8819088b30ef7b50598c9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d801acd9bc81908a23b1b7b4e778d3 |
completed | April 9, 2026, 7:44 p.m. |
| PD | Predicate disambiguation | batch_69d7e70ffd708190b62a78ebcbce9f78 |
completed | April 9, 2026, 5:51 p.m. |
Created at: April 8, 2026, 9:34 p.m.