Triple
T3680504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oregon–Washington football rivalry |
E78098
|
entity |
| Predicate | hasNicknameForTeam1 |
P5076
|
FINISHED |
| Object | Ducks |
—
|
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: Ducks | Statement: [Oregon–Washington football rivalry, hasNicknameForTeam1, Ducks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNicknameForTeam1 Context triple: [Oregon–Washington football rivalry, hasNicknameForTeam1, Ducks]
-
A.
notableTeamNickname
Indicates that a team is commonly known by a particular nickname that is notable or widely recognized.
-
B.
teamNickname
chosen
Indicates the commonly used informal or symbolic name by which a team is known.
-
C.
namedForTeam
Indicates that one entity has been given its name in honor of, or derived from, a particular team.
-
D.
isOfficialNicknameOf
Indicates that one name is the formally recognized nickname or informal moniker used to refer to another entity.
-
E.
associatedTeamName
Indicates the name of the team that is linked or connected to a given 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_69ad85e18c1c8190be8aafb227f39f48 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc49153ec81909ff3a3df54416d0e |
completed | March 8, 2026, 6:48 p.m. |
| PD | Predicate disambiguation | batch_69adb84be1fc81909721c871babb4633 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.