Triple
T7671952
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Wars prequel trilogy |
E173768
|
entity |
| Predicate | thirdFilmReleaseDate |
P36385
|
FINISHED |
| Object | 2005-05-19 |
—
|
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-05-19 | Statement: [Star Wars prequel trilogy, thirdFilmReleaseDate, 2005-05-19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdFilmReleaseDate Context triple: [Star Wars prequel trilogy, thirdFilmReleaseDate, 2005-05-19]
-
A.
thirdFilm
Indicates that one film is the third installment or entry in a sequence or series relative to another film.
-
B.
releaseDate_Theatrical
Indicates the date on which a work was first made publicly available in theaters.
-
C.
filmReleaseDate
chosen
Indicates the calendar date on which a film was first officially released or made publicly available.
-
D.
theatricalReleaseIn
Indicates that a film or performance was released or shown theatrically in a specified location or market.
-
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_69c699562484819086752091e3164a27 |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7063dab1881909598b04999b8b690 |
completed | March 27, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69c7015f7430819099d3ea2781b7cee2 |
completed | March 27, 2026, 10:14 p.m. |
Created at: March 27, 2026, 4 p.m.