Triple
T30884188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rainbow Records |
E786712
|
entity |
| Predicate | laterAdaptedInMedium |
P104271
|
FINISHED |
| Object | feature film |
—
|
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: feature film | Statement: [Rainbow Records, laterAdaptedInMedium, feature film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterAdaptedInMedium Context triple: [Rainbow Records, laterAdaptedInMedium, feature film]
-
A.
adaptationFromMedium
Indicates that one work is an adaptation derived from another work originally created in a different medium (e.g., book to film, comic to TV series).
-
B.
mediumAdaptation
chosen
Indicates that one work has been adapted into another form or medium (e.g., book to film, comic to TV series).
-
C.
laterAdaptedIn
Indicates that something was subsequently adapted, modified, or reworked in a later context, version, or medium.
-
D.
laterAdaptedFor
Indicates that something was subsequently modified or repurposed to serve a new use, context, or medium.
-
E.
subsequentMedium
Indicates that one medium or format follows another in a sequence, typically as a later or alternative form of the same content or communication.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ff136ed2a881908f713401083970d1 |
completed | May 9, 2026, 10:58 a.m. |
| PD | Predicate disambiguation | batch_69ff10f9e3448190b6cb6ea5a67713c1 |
completed | May 9, 2026, 10:48 a.m. |
Created at: April 29, 2026, 8:48 p.m.