Triple
T32280648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Before trilogy |
E824678
|
entity |
| Predicate | hasPartReleaseDate |
P172366
|
FINISHED |
| Object | Before Sunrise (1995) |
—
|
NE NERFINISHED |
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: Before Sunrise (1995) | Statement: [Before trilogy, hasPartReleaseDate, Before Sunrise (1995)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartReleaseDate Context triple: [Before trilogy, hasPartReleaseDate, Before Sunrise (1995)]
-
A.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
-
B.
materialReleased
Indicates that a material has been emitted, discharged, or otherwise released from its source into an environment or system.
-
C.
releaseDatePartOne
chosen
Indicates the date on which the first part or initial installment of something (such as a work, product, or series) is officially released.
-
D.
intendedForReleaseIn
Indicates that something is planned or scheduled to be made available or launched within a specified context, such as a time, market, or platform.
-
E.
fullyReleasedAs
Indicates that something has been completely made available or published in its final, unrestricted form.
- 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_69fef3ceef648190b58027c93d757438 |
completed | May 9, 2026, 8:43 a.m. |
| PD | Predicate disambiguation | batch_69fef359da2c819091a034387b08821f |
completed | May 9, 2026, 8:42 a.m. |
Created at: May 1, 2026, 12:43 a.m.