Triple
T29149574
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abra Kadabra |
E738865
|
entity |
| Predicate | primaryOpponentTeam |
P16339
|
FINISHED |
| Object | Flash Family |
—
|
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: Flash Family | Statement: [Abra Kadabra, primaryOpponentTeam, Flash Family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryOpponentTeam Context triple: [Abra Kadabra, primaryOpponentTeam, Flash Family]
-
A.
teamOpponent
Indicates that two teams are competing against each other as opponents in a game or match.
-
B.
finalOpponentTeam
Indicates the team that serves as the last or ultimate opposing team faced in a competition, series, or event.
-
C.
rivalTeam
chosen
Indicates that one team is in a competitive or adversarial relationship with another team, often vying for superiority or dominance.
-
D.
teamOpposed
Indicates that one team is in opposition or conflict with another team, such as being rivals or competing against each other.
-
E.
playoffOpponent
Indicates that two entities are matched to compete against each other in a playoff round or series.
- 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_69f07cb46f148190874eb8576a447567 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_6a00bcfed6448190b2e816bbe7c61c55 |
completed | May 10, 2026, 5:14 p.m. |
| PD | Predicate disambiguation | batch_6a00bc7be24c81908ba5c1957edd2c10 |
completed | May 10, 2026, 5:12 p.m. |
Created at: April 28, 2026, 11:41 a.m.