Triple
T21007674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sturgis Podmore |
E517455
|
entity |
| Predicate | actualCauseOfArrest |
P94805
|
FINISHED |
| Object | being under the Imperius Curse |
—
|
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: being under the Imperius Curse | Statement: [Sturgis Podmore, actualCauseOfArrest, being under the Imperius Curse]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actualCauseOfArrest Context triple: [Sturgis Podmore, actualCauseOfArrest, being under the Imperius Curse]
-
A.
hasReasonForArrest
chosen
Indicates that an arrest is associated with a specific reason or cause.
-
B.
arrestedFor
Indicates that an authority has taken someone into custody because they are suspected or accused of committing a specified offense or wrongdoing.
-
C.
arrestedWith
Indicates that two or more individuals were arrested at the same time and in connection with the same incident or operation.
-
D.
arrestIs
Indicates that one entity performs the action of arresting or taking another entity into legal custody.
-
E.
attemptedArrestBy
Indicates that one entity tried, but may not have succeeded, to place another entity under arrest.
- 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_69e0b50192308190a284fcc89dd23a49 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc3cc8648190b1a419ef734a69e6 |
completed | April 21, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:53 p.m.