Triple
T27726568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Up in the Sky (live) |
E697313
|
entity |
| Predicate | hasLiveVersionOf |
P45804
|
FINISHED |
| Object | Up in the Sky |
—
|
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: Up in the Sky | Statement: [Up in the Sky (live), hasLiveVersionOf, Up in the Sky]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveVersionOf Context triple: [Up in the Sky (live), hasLiveVersionOf, Up in the Sky]
-
A.
hasLiveVersions
chosen
Indicates that an entity has one or more recorded or documented live-performance versions of itself.
-
B.
isLiveVersion
Indicates that one entity is the current, active, or publicly available version of another entity.
-
C.
hasLiveActionVersion
Indicates that an entity has a corresponding adaptation or version produced in live-action (with real actors and physical settings) rather than animation or other non-live formats.
-
D.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
E.
hasVersionFor
Indicates that one entity serves as a specific version or variant tailored for another entity.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 27, 2026, 3:09 p.m.