Triple
T20210263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patronus Charm |
E493469
|
entity |
| Predicate | notableUserGroup |
P139204
|
FINISHED |
| Object | Order of the Phoenix members |
—
|
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: Order of the Phoenix members | Statement: [Patronus Charm, notableUserGroup, Order of the Phoenix members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableUserGroup Context triple: [Patronus Charm, notableUserGroup, Order of the Phoenix members]
-
A.
notableUser
Indicates that the user holds a special or distinguished status, such as being recognized, influential, or otherwise noteworthy within a given context.
-
B.
notableUserCommunity
Indicates that a user has a significant or distinguished presence, role, or recognition within a particular community.
-
C.
notableUserUnit
Indicates that a particular user is distinguished or recognized as notable within a given unit, group, or context.
-
D.
notableUserInterface
Indicates that an entity has a user interface that is particularly significant, prominent, or noteworthy in some context.
-
E.
notableSubgroup
Indicates that one group forms a particularly significant or noteworthy subset within a larger group.
- 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_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. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:38 p.m.