Triple
T20210254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patronus Charm |
E493469
|
entity |
| Predicate | canChangeWith |
P92084
|
FINISHED |
| Object | significant life events |
—
|
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: significant life events | Statement: [Patronus Charm, canChangeWith, significant life events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canChangeWith Context triple: [Patronus Charm, canChangeWith, significant life events]
-
A.
canSet
Indicates that one entity has the ability or permission to assign, configure, or change a property, value, or state of another entity.
-
B.
cannotChange
Indicates that an entity is unable or not permitted to alter the state, value, or properties of another entity or relationship.
-
C.
canChoose
Indicates that an entity has the ability or permission to select one option or entity from among alternatives.
-
D.
canElect
Indicates that one entity has the authority or ability to choose another entity for a position, role, or office through an election process.
-
E.
changesWith
chosen
Indicates that one entity varies or is modified in response to changes in 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66ed4706c81908a5e4a3023a9c22f |
completed | April 20, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:38 p.m.