Triple
T19985185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Department of Mysteries |
E493913
|
entity |
| Predicate | battleDateInFiction |
P58318
|
FINISHED |
| Object | June 1996 (wizarding world timeline) |
—
|
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: June 1996 (wizarding world timeline) | Statement: [Department of Mysteries, battleDateInFiction, June 1996 (wizarding world timeline)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: battleDateInFiction Context triple: [Department of Mysteries, battleDateInFiction, June 1996 (wizarding world timeline)]
-
A.
battleOccurredOn
Indicates that a specific battle took place at or on a particular location or date.
-
B.
battleOccurred
Indicates that a conflict or combat event took place between specified parties at a particular time and/or location.
-
C.
basedOnFictionalDateIn
chosen
Indicates that something is derived from, inspired by, or determined using a fictional date occurring within a specified work, timeline, or fictional context.
-
D.
battleDepicted
Indicates that a work or representation visually portrays a specific battle or combat event.
-
E.
battleAlsoKnownAs
Indicates that a particular battle is known by an alternative name or names.
- 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_69e537fae79c81909eae39500766d0b6 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 11, 2026, 3:29 p.m.