Triple
T11983371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raya and the Last Dragon |
E285212
|
entity |
| Predicate | releasedInFormat |
P59045
|
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: [Raya and the Last Dragon, releasedInFormat, theatrical release]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: releasedInFormat Context triple: [Raya and the Last Dragon, releasedInFormat, theatrical release]
-
A.
presentedInFormat
Indicates that something is expressed, delivered, or made available using a particular format or representation.
-
B.
typicalReleaseFormat
Indicates the usual or standard format in which something is released or published.
-
C.
fullyReleasedAs
Indicates that something has been completely made available or published in its final, unrestricted form.
-
D.
formatReleased
chosen
Indicates that a particular release or version of something is made available in a specified format (such as digital, physical, or a specific file type).
-
E.
firstReleaseFormat
Indicates the original medium or format in which something (such as a work or product) was first released.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903acbb9081908fe7f8360057785c |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902abca70819098291aa51b593708 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.