Triple
T23306942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marietta Edgecombe |
E590470
|
entity |
| Predicate | jinxTrigger |
P139694
|
FINISHED |
| Object | betrayal of Dumbledore's Army |
—
|
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: betrayal of Dumbledore's Army | Statement: [Marietta Edgecombe, jinxTrigger, betrayal of Dumbledore's Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jinxTrigger Context triple: [Marietta Edgecombe, jinxTrigger, betrayal of Dumbledore's Army]
-
A.
trapTrigger
Indicates that an entity activates or sets off a trap in the environment.
-
B.
magicTrigger
chosen
Indicates that one entity initiates or activates a magical effect, condition, or event upon another entity or context.
-
C.
trigger
Indicates that one entity causes or initiates an event, state, or action in another entity or system.
-
D.
usesTriggerSystem
Indicates that one entity operates or functions by means of a trigger-based mechanism or system provided or associated with another entity.
-
E.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
- 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_69e25d1c0ecc8190a355aa229f06d0e0 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972846fc819092ca2b9590b2e177 |
completed | April 29, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 5:05 p.m.