Triple
T19225080
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas Longhorns baseball games |
E480717
|
entity |
| Predicate | homeColorsDisplayed |
P26104
|
FINISHED |
| Object | burnt orange |
—
|
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: burnt orange | Statement: [Texas Longhorns baseball games, homeColorsDisplayed, burnt orange]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeColorsDisplayed Context triple: [Texas Longhorns baseball games, homeColorsDisplayed, burnt orange]
-
A.
homeColorsDominant
Indicates that the primary or most prominent colors associated with a subject’s home (such as a team’s home uniform or a building’s main color scheme) are specified or emphasized.
-
B.
homeKitTraditionalColor
Indicates that an entity’s color is represented using the traditional HomeKit color model or palette.
-
C.
colorVarietyOf
Indicates that one entity represents a specific color variant or color option of another entity.
-
D.
familyColor
Indicates that two entities share the same family-associated color or that one entity has a color characteristic of its family group.
-
E.
kitColorsHome
chosen
Indicates the colors used for a team's primary (home) kit or uniform.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fa97287c8190b85184a512a9c960 |
completed | April 20, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:24 p.m.