Triple
T8335937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quidditch |
E195784
|
entity |
| Predicate | hasFoulType |
P82160
|
FINISHED |
| Object | Blagging |
—
|
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: Blagging | Statement: [Quidditch, hasFoulType, Blagging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFoulType Context triple: [Quidditch, hasFoulType, Blagging]
-
A.
foulLimitPerTeam
Indicates the maximum number of fouls that a single team is allowed to commit within a defined game or competition context.
-
B.
penaltyFrom7thFoul
Indicates that a penalty situation arises as a result of committing a seventh foul.
-
C.
penaltyFrom10thFoul
Indicates that a penalty situation arises as a result of a team or player committing their tenth foul.
-
D.
forfeitedBy
Indicates that something (such as a right, claim, or asset) is lost or given up as a consequence of the actions or failure of a particular entity.
-
E.
hasPunishment
Indicates that an entity is subject to a specified penalty, sanction, or adverse consequence as a result of some action, condition, or rule.
- 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_69ca82ecbdc481908a55cad8ca062d88 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb7fd3fc80819097b326119107ad4d |
completed | March 31, 2026, 8:03 a.m. |
| PD | Predicate disambiguation | batch_69cb70c3231c81909e3d463192c9de22 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb76d823b08190a54fadb50660cda5 |
completed | March 31, 2026, 7:25 a.m. |
Created at: March 30, 2026, 5:57 p.m.