Triple
T489946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harvard Crimson men’s soccer |
E9963
|
entity |
| Predicate | nickname |
P55
|
FINISHED |
| Object | Crimson |
E308
|
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: Crimson | Statement: [Harvard Crimson men’s soccer, nickname, Crimson]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Crimson Context triple: [Harvard Crimson men’s soccer, nickname, Crimson]
-
A.
Crimson
chosen
Crimson is the collective name for Harvard University's varsity athletic teams competing in collegiate sports.
-
B.
Black-and-Red
Black-and-Red is the widely used nickname for Major League Soccer club D.C. United, referencing the team’s traditional colors and identity.
-
C.
Orange
Orange is a historic town in southeastern France best known for giving its name and origin to the Dutch royal House of Orange-Nassau.
-
D.
Red 1
Red 1 is the callsign used by the team leader of the Royal Air Force's Red Arrows aerobatic display team.
-
E.
Scarlet Knight
Scarlet Knight is the armored medieval knight mascot representing Rutgers University's athletic teams.
- 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_69a2e802e2908190ab17c9479e0b6412 |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f0e0a9648190b6a3b2da3a3b51e6 |
completed | Feb. 28, 2026, 1:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a474738bb881908e5d0ff6a17301e8 |
completed | March 1, 2026, 5:16 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.