Triple
T370004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yale Bulldogs |
E8246
|
entity |
| Predicate | hasColor |
P60
|
FINISHED |
| Object | Yale Blue |
E1533
|
NE 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: Yale Blue | Statement: [Yale Bulldogs, hasColor, Yale Blue]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yale Blue Context triple: [Yale Bulldogs, hasColor, Yale Blue]
-
A.
Yale Blue
chosen
Yale Blue is a deep, rich shade of blue traditionally associated with academic institutions and collegiate branding.
-
B.
Duke blue
Duke blue is the distinctive deep royal blue shade associated with Duke University’s branding and athletic teams.
-
C.
Oxford blue
Oxford blue is a dark, rich shade of navy traditionally associated with the University of Oxford and its sports teams.
-
D.
Yale Bulldogs
The Yale Bulldogs are the varsity athletic teams representing Yale University in NCAA Division I sports, particularly known for their historic football and ice hockey programs.
-
E.
Harvard Crimson
Harvard Crimson is the collective name for Harvard University's varsity athletic teams, which compete in NCAA Division I as part of the Ivy League.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a2e7f2ec648190b42bc7db424f8109 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebfdb0608190b1794a871d0d237a |
completed | Feb. 28, 2026, 1:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a3ecac7e048190a76c02c738599c61 |
completed | March 1, 2026, 7:37 a.m. |
Created at: Feb. 28, 2026, 1:08 p.m.