Triple
T9427777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reputation Stadium Tour |
E227297
|
entity |
| Predicate | concertFilmReleaseDate |
P36385
|
FINISHED |
| Object | 2018-12-31 |
—
|
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: 2018-12-31 | Statement: [Reputation Stadium Tour, concertFilmReleaseDate, 2018-12-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concertFilmReleaseDate Context triple: [Reputation Stadium Tour, concertFilmReleaseDate, 2018-12-31]
-
A.
filmReleaseDate
chosen
Indicates the calendar date on which a film was first officially released or made publicly available.
-
B.
theatricalReleaseIn
Indicates that a film or performance was released or shown theatrically in a specified location or market.
-
C.
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.
-
D.
filmReleaseYear
Indicates the calendar year in which a film was first officially released to the public.
-
E.
filmReleaseContext
Indicates the circumstances or setting (such as time, place, or format) under which a film is released.
- 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_69ca8436ba308190903e470776d2d893 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7c91ba1c8190b8331fb1ba58cc61 |
completed | April 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:49 p.m.