Triple
T28639031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quaffle |
E724868
|
entity |
| Predicate | thrownThrough |
P165162
|
FINISHED |
| Object | Quidditch goal hoops |
—
|
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: Quidditch goal hoops | Statement: [Quaffle, thrownThrough, Quidditch goal hoops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thrownThrough Context triple: [Quaffle, thrownThrough, Quidditch goal hoops]
-
A.
throws
Indicates that one entity propels or hurls another entity or object through space, typically by a deliberate physical action.
-
B.
wasThrownFrom
Indicates that an entity was propelled away or ejected from another entity, typically by a forceful or intentional throwing action.
-
C.
throwingImplement
Indicates that an entity uses or propels an implement (such as a tool, weapon, or object) by throwing it.
-
D.
throwsUpTo
Indicates that an entity propels or sends something in an upward direction toward a specified target or limit.
-
E.
shotThrough
Indicates that one entity has been pierced or passed through by a projectile or similar object fired from another entity.
- 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_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 28, 2026, 4:42 a.m.