Triple
T28639025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quaffle |
E724868
|
entity |
| Predicate | weightComparedTo |
P1575
|
FINISHED |
| Object | similar to a Muggle football |
—
|
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: similar to a Muggle football | Statement: [Quaffle, weightComparedTo, similar to a Muggle football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weightComparedTo Context triple: [Quaffle, weightComparedTo, similar to a Muggle football]
-
A.
weightCondition
Indicates that a specified weight-related requirement or constraint holds between entities or values.
-
B.
weight
chosen
Indicates a relationship where a numerical value quantifies how heavy an entity is, often used to measure or compare mass or load.
-
C.
وزن
Indicates a relationship where one entity has, measures, or is characterized by a certain weight or mass.
-
D.
weightSize
Indicates a relationship between an entity’s weight and its physical size, typically expressing how one varies or is characterized in terms of the other.
-
E.
isHeavierThan
Indicates that one entity has greater weight or mass than another entity.
- 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 4:42 a.m.