Triple
T19985569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muggle Studies |
E493921
|
entity |
| Predicate | ideologyUnderAlectoCarrow |
P496
|
FINISHED |
| Object | pro-wizard supremacy |
—
|
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: pro-wizard supremacy | Statement: [Muggle Studies, ideologyUnderAlectoCarrow, pro-wizard supremacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ideologyUnderAlectoCarrow Context triple: [Muggle Studies, ideologyUnderAlectoCarrow, pro-wizard supremacy]
-
A.
opposingFactionIdeology
Indicates that two factions hold ideologies that are in direct conflict or fundamental opposition to each other.
-
B.
ideology
chosen
Indicates the belief system or set of political, social, or philosophical principles that an entity adheres to or promotes.
-
C.
ideologyComponent
Indicates that one ideology is a constituent or defining part of another, broader ideology.
-
D.
ideologyNamedAfter
Indicates that an ideology is named after a particular person, group, place, or entity.
-
E.
ideologyDevelopment
Indicates the process by which an ideology forms, evolves, or is shaped over time through influences, interpretations, and contextual factors.
- 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_69da626a67648190af9653832a3aeced |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e65d162b008190a18d325796d75d77 |
completed | April 20, 2026, 5:06 p.m. |
| PD | Predicate disambiguation | batch_69e537fd311881908448f2aea8b4812e |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:29 p.m.