Triple
T32280489
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Predestination |
E824674
|
entity |
| Predicate | theatricalReleaseDateInAustralia |
P22093
|
FINISHED |
| Object | 2014-08-28 |
—
|
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: 2014-08-28 | Statement: [Predestination, theatricalReleaseDateInAustralia, 2014-08-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: theatricalReleaseDateInAustralia Context triple: [Predestination, theatricalReleaseDateInAustralia, 2014-08-28]
-
A.
theatricalReleaseYearInAustralia
Indicates the calendar year in which a work was first theatrically released in Australia.
-
B.
releaseDateAustralia
chosen
Indicates the date on which something is officially released or made available in Australia.
-
C.
theatricalReleaseDateUS
Indicates the calendar date on which a work was first released theatrically in the United States.
-
D.
theatricalReleaseDateCanada
Indicates the calendar date on which a film or similar work was first released theatrically in Canada.
-
E.
theatricalReleaseDateUK
Indicates the calendar date on which a work was first released theatrically in the United Kingdom.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bcc7edfc81909d0008fa9364de54 |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:43 a.m.