Triple
T9028635
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 34 (Len Bias) |
E216109
|
entity |
| Predicate | jerseyColorContext |
P85963
|
FINISHED |
| Object | Maryland Terrapins team colors |
—
|
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: Maryland Terrapins team colors | Statement: [34 (Len Bias), jerseyColorContext, Maryland Terrapins team colors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jerseyColorContext Context triple: [34 (Len Bias), jerseyColorContext, Maryland Terrapins team colors]
-
A.
jerseyColorPrimary
Indicates the main or dominant color used on an entity’s jersey or uniform.
-
B.
jerseyColorThemeOfHost
Indicates that a specified jersey color theme is used by the host team or host entity in an event or competition.
-
C.
jerseyColorTradition
Indicates a conventional or historically established association between a team and the primary color of its jersey.
-
D.
jerseyColorReason
Indicates the reason or basis for why an entity has a particular jersey color.
-
E.
jerseyColourAway
Indicates the color of the jersey worn by a team when playing away from their home venue.
- F. None of above. chosen
Provenance (4 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_69ca83a5fa88819088144801b4dd7245 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6a7fcb308190af90d6be8700e498 |
completed | April 1, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cc5ee132f08190940749c7c522e4c1 |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5f887108819096d45a186fc137b3 |
completed | March 31, 2026, 11:58 p.m. |
Created at: March 30, 2026, 7:08 p.m.