Triple
T23969106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Visit (2000 film) |
E604176
|
entity |
| Predicate | theatricalReleaseType |
P154069
|
FINISHED |
| Object | independent |
—
|
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: independent | Statement: [The Visit (2000 film), theatricalReleaseType, independent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: theatricalReleaseType Context triple: [The Visit (2000 film), theatricalReleaseType, independent]
-
A.
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.
-
B.
hasTheatricalForm
Indicates that something is associated with or presented in a particular theatrical form or style.
-
C.
theatricalReleaseIn
Indicates that a film or performance was released or shown theatrically in a specified location or market.
-
D.
theaterType
Indicates the specific kind or category of theater associated with an entity (e.g., cinema, opera house, drama theater).
-
E.
releaseDate_Theatrical
Indicates the date on which a work was first made publicly available in theaters.
- F. None of above. chosen
Provenance (4 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d1da2ab08190bfe653fb5a9f2c96 |
completed | April 29, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 9:25 p.m.