Triple
T28639116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Snitch |
E724870
|
entity |
| Predicate | roleInQuidditch |
P197126
|
FINISHED |
| Object | determines end of match when caught |
—
|
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: determines end of match when caught | Statement: [Golden Snitch, roleInQuidditch, determines end of match when caught]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInQuidditch Context triple: [Golden Snitch, roleInQuidditch, determines end of match when caught]
-
A.
playsQuidditchWith
Indicates that two or more entities participate together as teammates or co-players in a game of Quidditch.
-
B.
wasQuidditchCaptain
Indicates that an entity held the role of captain of a Quidditch team.
-
C.
roleInHarryPotter
Indicates that one entity has a specific role or character part within the Harry Potter series in relation to the other entity.
-
D.
quidditchSkill
Indicates the level or quality of an entity’s ability to play or perform in Quidditch.
-
E.
roleInSoccer
Indicates the specific function or position an entity holds within the context of playing or organizing a soccer game.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
| PDg | Predicate description generation | batch_69fe78e35e6c8190b8b440777912f64e |
completed | May 8, 2026, 11:59 p.m. |
Created at: April 28, 2026, 4:43 a.m.