Triple
T32720989
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avatar 5 |
E836671
|
entity |
| Predicate | intendedReleaseMedium |
P85649
|
FINISHED |
| Object | theatrical release |
—
|
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 release | Statement: [Avatar 5, intendedReleaseMedium, theatrical release]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedReleaseMedium Context triple: [Avatar 5, intendedReleaseMedium, theatrical release]
-
A.
hasReleaseMedium
chosen
Indicates the medium or format through which something (such as a work or product) is released or made available.
-
B.
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.
-
C.
typicalReleaseFormat
Indicates the usual or standard format in which something is released or published.
-
D.
hasPhysicalMedium
Indicates that one entity serves as the tangible carrier or material form through which another entity exists, is stored, or is transmitted.
-
E.
volumeReleased
Indicates that a specific volume (such as a book, issue, or installment) has been officially released or made publicly available.
- 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_69f34935455881909088975d79460418 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: May 1, 2026, 1:11 a.m.