Triple
T22575091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No Fear of Time |
E544371
|
entity |
| Predicate | hasReleaseStrategy |
P19968
|
FINISHED |
| Object | exclusive initial release on Luminary |
—
|
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: exclusive initial release on Luminary | Statement: [No Fear of Time, hasReleaseStrategy, exclusive initial release on Luminary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReleaseStrategy Context triple: [No Fear of Time, hasReleaseStrategy, exclusive initial release on Luminary]
-
A.
hasRelease
Indicates that an entity (such as a product, work, or version) has a specific release instance or event associated with it.
-
B.
hasReleaseBranch
Indicates that an entity is associated with a specific release branch, typically representing a stabilized version line in a version control or release management system.
-
C.
hasReleaseGeneration
Indicates that one entity is associated with a particular release generation or version cycle of another entity.
-
D.
hasReleaseModel
chosen
Indicates the type or strategy of release associated with an entity, such as how or under what model it is made available.
-
E.
hasReleased
Indicates that an entity has made another entity publicly available or officially launched it.
- 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_69e11e30d05481909df915354c89f0d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f15fec296481908a6101b02e5bedaa |
completed | April 29, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:53 p.m.