Triple
T3860498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roadside Attractions |
E90121
|
entity |
| Predicate | primaryReleaseWindow |
P51479
|
FINISHED |
| Object | theatrical |
—
|
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: theatrical | Statement: [Roadside Attractions, primaryReleaseWindow, theatrical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryReleaseWindow Context triple: [Roadside Attractions, primaryReleaseWindow, theatrical]
-
A.
publicRelease
Indicates that something is made available to the general public, typically after any private or restricted access period has ended.
-
B.
initialReleaseWith
Indicates that two or more entities were first released together as part of the same initial release event or package.
-
C.
firstRelease
Indicates that one entity is the initial or earliest release (in time or sequence) of another entity, such as a product, work, or version.
-
D.
releasedThrough
chosen
Indicates that something (such as a work, product, or content) is made publicly available or distributed via a particular channel, platform, or intermediary.
-
E.
releaseStatus
Indicates the current state or phase of an item’s release process (e.g., planned, in progress, or completed).
- 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_69aed95b3c088190a8f85d19e6070599 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeec212a1c8190aba6311630c3fd3e |
completed | March 9, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69aee752c8a48190a670f73ed0bf1e61 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:19 p.m.