Triple
T3795471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harry Potter and the Goblet of Fire |
E89757
|
entity |
| Predicate | filmAdaptationReleaseDate |
P36385
|
FINISHED |
| Object | 2005-11-18 |
—
|
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: 2005-11-18 | Statement: [Harry Potter and the Goblet of Fire, filmAdaptationReleaseDate, 2005-11-18]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filmAdaptationReleaseDate Context triple: [Harry Potter and the Goblet of Fire, filmAdaptationReleaseDate, 2005-11-18]
-
A.
filmReleaseDate
chosen
Indicates the calendar date on which a film was first officially released or made publicly available.
-
B.
filmAdaptationStudio
Indicates that a particular studio is responsible for producing or creating the film adaptation of a work.
-
C.
adaptationReleaseYear
Indicates the year in which an adaptation of a work was released.
-
D.
filmReleaseYear
Indicates the calendar year in which a film was first officially released to the public.
-
E.
theatricalReleaseWith
Indicates that two or more entities share the same theatrical release context, such as being released together or as part of the same theatrical event or distribution.
- 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_69aed9597d6881909b6ee3b9de859223 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecefa3608190a7a20ed6df6a64b2 |
completed | March 9, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69aee743c8d08190a9f9c97b836bd703 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.