Triple
T33865214
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sea of Red |
E868028
|
entity |
| Predicate | fanBaseNicknameContext |
P5382
|
FINISHED |
| Object | Nebraska Cornhuskers fans |
—
|
NE NERFINISHED |
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: Nebraska Cornhuskers fans | Statement: [The Sea of Red, fanBaseNicknameContext, Nebraska Cornhuskers fans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fanBaseNicknameContext Context triple: [The Sea of Red, fanBaseNicknameContext, Nebraska Cornhuskers fans]
-
A.
fanBaseName
Indicates the name by which the collective group of fans of a particular person, group, or entity is known.
-
B.
fanNicknameForFixture
Indicates that a particular nickname is used by fans to refer to a specific fixture or matchup.
-
C.
fanBase1
Indicates that one entity serves as the primary or original fan base supporting another entity.
-
D.
cityNickNameForFanBase
chosen
Indicates that a particular nickname is used by fans to refer to a city or its fan base.
-
E.
fanBase
Indicates that one entity is the group of admirers or supporters devoted to another entity.
- 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_69f34995029081909ede0f7df73d1a5e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f700a15edc8190a338cb7d5b703b9d |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5a4f7881909324eb3c20ca96f1 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.