Triple
T38218555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Fantastic Four (1994 film) |
E1010747
|
entity |
| Predicate | intendedReleaseStatus |
P196891
|
FINISHED |
| Object | unreleased |
—
|
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: unreleased | Statement: [The Fantastic Four (1994 film), intendedReleaseStatus, unreleased]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedReleaseStatus Context triple: [The Fantastic Four (1994 film), intendedReleaseStatus, unreleased]
-
A.
intendedForReleaseIn
Indicates that something is planned or scheduled to be made available or launched within a specified context, such as a time, market, or platform.
-
B.
originalReleaseStatus
Indicates the publication or distribution state of a work at the time of its initial release.
-
C.
releaseStatus
Indicates the current state or phase of an item’s release process (e.g., planned, in progress, or completed).
-
D.
stableReleaseStatus
Indicates the release status or condition of a stable version of something (such as software or a product).
-
E.
reReleaseStatus
Indicates the release state or condition of something in relation to a prior or original release.
- 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_69f76dcdc7708190a5f1751d53f40ffe |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe6c811bcc81908b1e1b1f8bcb071b |
completed | May 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69fe6c026d5481908b7a814dcf38c183 |
completed | May 8, 2026, 11:04 p.m. |
| PDg | Predicate description generation | batch_69fe6c7fc4388190aa88993d00872d7f |
completed | May 8, 2026, 11:06 p.m. |
Created at: May 3, 2026, 4:30 p.m.