Triple
T27357962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Avatar 4 |
E685737
|
entity |
| Predicate | intendedForReleaseIn |
P173218
|
FINISHED |
| Object | movie theaters |
—
|
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: movie theaters | Statement: [Avatar 4, intendedForReleaseIn, movie theaters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedForReleaseIn Context triple: [Avatar 4, intendedForReleaseIn, movie theaters]
-
A.
originallyScheduledReleaseDate
Indicates the date on which something was first planned or intended to be released, before any later changes or rescheduling.
-
B.
previewReleaseDate
Indicates the date on which a preview or pre-release version of something is or was made available.
-
C.
stableReleaseApproxDate
Indicates an approximate calendar date when a stable release of something is (or was) expected to become available.
-
D.
initialReleaseFor
Indicates that one entity is the first or original release version associated with another entity (such as a work, product, or edition).
-
E.
fullyReleasedAs
Indicates that something has been completely made available or published in its final, unrestricted form.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 27, 2026, 11:52 a.m.