Triple
T24008881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doris Day–Rock Hudson film collaborations |
E594467
|
entity |
| Predicate | hasReleasePattern |
P154847
|
FINISHED |
| Object | theatrical feature films |
—
|
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 feature films | Statement: [Doris Day–Rock Hudson film collaborations, hasReleasePattern, theatrical feature films]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReleasePattern Context triple: [Doris Day–Rock Hudson film collaborations, hasReleasePattern, theatrical feature films]
-
A.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
-
B.
hasReleaseModel
Indicates the type or strategy of release associated with an entity, such as how or under what model it is made available.
-
C.
hasReleaseBranch
Indicates that an entity is associated with a specific release branch, typically representing a stabilized version line in a version control or release management system.
-
D.
hasReleaseGeneration
Indicates that one entity is associated with a particular release generation or version cycle of another entity.
-
E.
hasScheduledReleases
Indicates that an entity has one or more releases planned to occur at specific future times.
- 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_69e288bc8f608190ac4af29f0bd1c744 |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d46c77f88190806e6287e55c9136 |
completed | April 29, 2026, 9:50 a.m. |
| PD | Predicate disambiguation | batch_69f17639d23c8190bed93434e2f9230a |
completed | April 29, 2026, 3:08 a.m. |
| PDg | Predicate description generation | batch_69f17c28b684819084eea522126463f8 |
completed | April 29, 2026, 3:34 a.m. |
Created at: April 17, 2026, 9:41 p.m.