Triple
T33446056
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Pink Panther 3 (planned film) |
E856505
|
entity |
| Predicate | plannedReleasePeriod |
P173218
|
FINISHED |
| Object | 2010s |
—
|
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: 2010s | Statement: [The Pink Panther 3 (planned film), plannedReleasePeriod, 2010s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedReleasePeriod Context triple: [The Pink Panther 3 (planned film), plannedReleasePeriod, 2010s]
-
A.
intendedForReleaseIn
chosen
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.
stableReleaseApproxDate
Indicates an approximate calendar date when a stable release of something is (or was) expected to become available.
-
C.
previewReleaseDate
Indicates the date on which a preview or pre-release version of something is or was made available.
-
D.
originallyScheduledReleaseDate
Indicates the date on which something was first planned or intended to be released, before any later changes or rescheduling.
-
E.
plannedAt
Indicates that an event, action, or activity is scheduled or intended to occur at a specific time or date.
- 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 1, 2026, 1:37 a.m.