Triple
T9879700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Renaissance World Tour |
E240167
|
entity |
| Predicate | associatedFilmReleaseYear |
P56244
|
FINISHED |
| Object | 2023 |
—
|
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: 2023 | Statement: [Renaissance World Tour, associatedFilmReleaseYear, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedFilmReleaseYear Context triple: [Renaissance World Tour, associatedFilmReleaseYear, 2023]
-
A.
filmReleaseYear
Indicates the calendar year in which a film was first officially released to the public.
-
B.
associatedWithYearFilm
chosen
Indicates a relationship where something (such as an event, award, or record) is linked to or pertains to a specific film released or identified in a given year.
-
C.
yearOfFilmAppearance
Indicates the specific year in which a film appearance by an entity took place.
-
D.
filmReleaseDate
Indicates the calendar date on which a film was first officially released or made publicly available.
-
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_69ca84e8a0788190b9061811d50fd554 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb4146fe881908f9fc553dfca31e1 |
completed | April 2, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69cd1d810ed48190a252b70e9390c8f3 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:37 p.m.