Triple
T19583464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orphans of the Sky |
E490051
|
entity |
| Predicate | originalComponentWork |
P136349
|
FINISHED |
| Object | Universe |
—
|
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: Universe | Statement: [Orphans of the Sky, originalComponentWork, Universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalComponentWork Context triple: [Orphans of the Sky, originalComponentWork, Universe]
-
A.
originalWorkFrom
Indicates that something is derived, adapted, or based on an earlier original work created by another source.
-
B.
originalWorkInstanceOf
Indicates that an original work is a specific instance or realization of a more general work, type, or conceptual creation.
-
C.
originalPublicationOfWholeWork
Indicates that one entity is the original publication in which an entire work was first made publicly available.
-
D.
originalWorkMovement
Indicates the artistic, cultural, or intellectual movement or style with which the original work is associated or classified.
-
E.
firstWork
Indicates that the related work is the earliest or initial work created, published, or produced by the entity in question.
- 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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6404f34b081908aeb9cc9a5ddf539 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
| PDg | Predicate description generation | batch_69e5174b060c81908937ff9ff7fce611 |
completed | April 19, 2026, 5:56 p.m. |
Created at: April 10, 2026, 1:42 p.m.