Triple
T31394939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duke vs. North Carolina games |
E800839
|
entity |
| Predicate | colorAssociationUNC |
P65875
|
FINISHED |
| Object | Carolina blue |
—
|
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: Carolina blue | Statement: [Duke vs. North Carolina games, colorAssociationUNC, Carolina blue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colorAssociationUNC Context triple: [Duke vs. North Carolina games, colorAssociationUNC, Carolina blue]
-
A.
colorAssociatedInstitution
Indicates that a particular color is characteristically linked or symbolically connected to an institution.
-
B.
colorUse
Indicates that one entity uses, applies, or is associated with a particular color in its appearance, design, or representation.
-
C.
colorSystem
Indicates that one entity is a system or scheme used to define, organize, or represent the colors of another entity.
-
D.
associatedColour
chosen
Indicates that one entity is linked to another as its characteristic or representative colour.
-
E.
colorStates
Indicates that an entity has or is associated with one or more specific color conditions or statuses.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f73223675481908c1bc3208c0f5284 |
completed | May 3, 2026, 11:31 a.m. |
| PD | Predicate disambiguation | batch_69f7317690108190b3aae2cd2e1d069e |
completed | May 3, 2026, 11:28 a.m. |
Created at: April 29, 2026, 9:19 p.m.