Triple
T25488709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D2: The Mighty Ducks |
E638780
|
entity |
| Predicate | notableOpponentTeam |
P26732
|
FINISHED |
| Object | Team Iceland |
—
|
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: Team Iceland | Statement: [D2: The Mighty Ducks, notableOpponentTeam, Team Iceland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableOpponentTeam Context triple: [D2: The Mighty Ducks, notableOpponentTeam, Team Iceland]
-
A.
notableRivalTeam
chosen
Indicates that one team is recognized as a significant or well-known rival of another team.
-
B.
notableRivalOpponent
Indicates that one entity is a particularly significant or well-known rival or opponent of another entity.
-
C.
opposingTeamInNotableEvent
Indicates that one entity served as the opposing team of another entity in a specific notable event or competition.
-
D.
notableOpponentTeamMember
Indicates that a specific team member is recognized as a particularly significant or noteworthy opponent in relation to another entity or context.
-
E.
notableCompetitorPairs
Indicates that the two entities form a pair of organizations or individuals that are notably recognized as competitors with each other.
- 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_69e75dbabeac8190bab30628f8b799d4 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69fcf825ca7081909d06b0df33eb33f9 |
completed | May 7, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fcf42160f0819096812a8bf590875e |
completed | May 7, 2026, 8:20 p.m. |
Created at: April 21, 2026, 2:34 p.m.