Triple
T27764443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cabin Crew – Star to Fall |
E701561
|
entity |
| Predicate | isModernReworkingOf |
P109036
|
FINISHED |
| Object | Waiting for a Star to Fall |
—
|
NE NERFINISHED |
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: Waiting for a Star to Fall | Statement: [Cabin Crew – Star to Fall, isModernReworkingOf, Waiting for a Star to Fall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isModernReworkingOf Context triple: [Cabin Crew – Star to Fall, isModernReworkingOf, Waiting for a Star to Fall]
-
A.
isModernizationOf
chosen
Indicates that one entity is an updated, improved, or contemporary version of another earlier entity.
-
B.
hasRemake
Indicates that one work is a new version or recreation of an earlier existing work.
-
C.
isModern
Indicates that something belongs to, reflects, or is characteristic of the contemporary or recent period, especially in style, design, or thinking.
-
D.
hasRemakeOrRetroVersion
Indicates that one work has been remade or re-released in a retro-style version of the original.
-
E.
isIndirectRemakeOf
Indicates that one work is a remake of another, but derived through an intermediate adaptation rather than directly from the original.
- 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_69ef6a52fa708190934a32308d2c92dc |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63767994c8190a1aca30930233c51 |
completed | May 2, 2026, 5:41 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 4:29 p.m.