Triple
T19984709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Wizarding War |
E493903
|
entity |
| Predicate | chronologicallySetAfter |
P6880
|
FINISHED |
| Object | events of Harry Potter and the Goblet of Fire |
—
|
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: events of Harry Potter and the Goblet of Fire | Statement: [Second Wizarding War, chronologicallySetAfter, events of Harry Potter and the Goblet of Fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chronologicallySetAfter Context triple: [Second Wizarding War, chronologicallySetAfter, events of Harry Potter and the Goblet of Fire]
-
A.
chronologicallyAfter
chosen
Indicates that one event or state occurs later in time than another.
-
B.
chronologicallyOrdered
Indicates that the related entities are arranged in the order in which they occur in time.
-
C.
chronologicallyOrders
Indicates that one entity arranges or sequences other entities according to their positions in time, from earlier to later.
-
D.
tookPlaceAfter
Indicates that one event or occurrence happened later in time than another event or occurrence.
-
E.
chronologicallySucceededBy
Indicates that one event or state occurs later in time than, and thus follows, another.
- 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_69e65d157d088190af861608936e59b7 |
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.