Triple
T20210331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Witherwings |
E493471
|
entity |
| Predicate | usedAsAliasToAvoid |
P6275
|
FINISHED |
| Object | Ministry of Magic detection |
—
|
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: Ministry of Magic detection | Statement: [Witherwings, usedAsAliasToAvoid, Ministry of Magic detection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsAliasToAvoid Context triple: [Witherwings, usedAsAliasToAvoid, Ministry of Magic detection]
-
A.
usesAliasTo
Indicates that one entity employs an alternative name or identifier to refer to or represent another entity.
-
B.
usesAliasFor
Indicates that one entity employs an alternative name or identifier to refer to another entity.
-
C.
usedByAlias
Indicates that something is utilized, referenced, or accessed through an alternative name or alias.
-
D.
nameUsedToAvoid
chosen
Indicates that one entity uses a particular name or designation in order to avoid another entity or an unwanted situation involving that entity.
-
E.
renamedToAvoidConfusionWith
Indicates that one entity’s name was changed specifically to prevent it from being mistaken for 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.