Triple
T32280233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American (wizarding world) |
E824668
|
entity |
| Predicate | hasKnownQuidditchLeague |
P173918
|
FINISHED |
| Object | American National Quidditch League |
—
|
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: American National Quidditch League | Statement: [American (wizarding world), hasKnownQuidditchLeague, American National Quidditch League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasKnownQuidditchLeague Context triple: [American (wizarding world), hasKnownQuidditchLeague, American National Quidditch League]
-
A.
quidditchCupWins
Indicates the number of times an entity has won the Quidditch Cup in competitive play.
-
B.
sharesTriwizardCupWith
Indicates that two participants jointly possess or are co-winners of the Triwizard Cup in the same event.
-
C.
playsQuidditchWith
Indicates that two or more entities participate together as teammates or co-players in a game of Quidditch.
-
D.
houseQuidditchTeam
Indicates that a particular Quidditch team is the official team representing a specific Hogwarts house.
-
E.
wasQuidditchCaptain
Indicates that an entity held the role of captain of a Quidditch team.
- F. None of above. chosen
Provenance (4 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_69f6bcc7edfc81909d0008fa9364de54 |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b960ca4081909a77690c2b122f5e |
completed | May 3, 2026, 2:56 a.m. |
Created at: May 1, 2026, 12:43 a.m.