Triple
T33865209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Sea of Red |
E868028
|
entity |
| Predicate | homeVenueNicknameFor |
P9350
|
FINISHED |
| Object | Nebraska Cornhuskers football team |
—
|
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 football team | Statement: [The Sea of Red, homeVenueNicknameFor, Nebraska Cornhuskers football team]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeVenueNicknameFor Context triple: [The Sea of Red, homeVenueNicknameFor, Nebraska Cornhuskers football team]
-
A.
homeVenueName
Indicates the name of the primary venue or location where an entity (such as a team, event, or organization) regularly hosts its home activities.
-
B.
homeVenueCurrentName
Indicates the current official name of the venue that serves as an entity’s home location.
-
C.
homeArenaNickname
chosen
Indicates the commonly used or informal nickname of a team's or organization's home arena.
-
D.
homeVenueTeam1City
Indicates that a specific city serves as the home venue location for the first team in a given context or event.
-
E.
houseNickname
Indicates that an entity has an informal or alternative name used as a nickname for a house or dwelling.
- 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.