Triple
T16165872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grown Ups 3 |
E392300
|
entity |
| Predicate | hasReleaseStatus |
P9940
|
FINISHED |
| Object | not on any official release schedule as of 2024 |
—
|
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: not on any official release schedule as of 2024 | Statement: [Grown Ups 3, hasReleaseStatus, not on any official release schedule as of 2024]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReleaseStatus Context triple: [Grown Ups 3, hasReleaseStatus, not on any official release schedule as of 2024]
-
A.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
-
B.
stableReleaseStatus
Indicates the release status or condition of a stable version of something (such as software or a product).
-
C.
releaseStatus
chosen
Indicates the current state or phase of an item’s release process (e.g., planned, in progress, or completed).
-
D.
hasReleaseModel
Indicates the type or strategy of release associated with an entity, such as how or under what model it is made available.
-
E.
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.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21eb2a25c819095437b25e6ab83f3 |
completed | April 17, 2026, 11:51 a.m. |
| PD | Predicate disambiguation | batch_69e1828abb608190a99d86bce1d77de2 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:02 a.m.