Triple
T28728378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ravenclaw Quidditch team |
E730287
|
entity |
| Predicate | chaser |
P165553
|
FINISHED |
| Object | Roger Davies |
—
|
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: Roger Davies | Statement: [Ravenclaw Quidditch team, chaser, Roger Davies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chaser Context triple: [Ravenclaw Quidditch team, chaser, Roger Davies]
-
A.
chases
Indicates that one entity actively pursues another, typically moving after it in an attempt to catch or reach it.
-
B.
challenger
Indicates that one entity is challenging or opposing another, typically by initiating a contest, dispute, or competitive confrontation.
-
C.
Chi Chi
Indicates a relationship or action involving an entity named "Chi Chi," such as interaction, association, or effect directed to or from Chi Chi.
-
D.
chasesAcross
Indicates that one entity actively pursues another entity while moving from one side or area to another across some intervening space or surface.
-
E.
chasedAway
Indicates that one entity caused another to flee or leave a place, typically through pursuit, threat, or intimidation.
- 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_69f043e91fe48190b73bcd8e08d433e0 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f6596b210481908af6cd555748f75b |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 5:57 a.m.