Triple
T32280232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American (wizarding world) |
E824668
|
entity |
| Predicate | hasPopularSportVariant |
P55114
|
FINISHED |
| Object | Quadpot |
—
|
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: Quadpot | Statement: [American (wizarding world), hasPopularSportVariant, Quadpot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPopularSportVariant Context triple: [American (wizarding world), hasPopularSportVariant, Quadpot]
-
A.
hasEsport
Indicates that an entity is associated with or participates in a specific electronic sports (esports) activity or competition.
-
B.
includesSport
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
-
C.
hasAlternativeSport
Indicates that an entity is associated with another sport that can serve as a substitute or alternative option.
-
D.
sportsVariant
chosen
Indicates that one sport is a variation, subtype, or modified form of another sport.
-
E.
appliesToSportType
Indicates that something is relevant or specifically associated with a particular type or category of sport.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
Created at: May 1, 2026, 12:43 a.m.