Triple
T27726550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cloudburst |
E697312
|
entity |
| Predicate | followsInReleaseContext |
P86044
|
FINISHED |
| Object | early Oasis singles |
—
|
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: early Oasis singles | Statement: [Cloudburst, followsInReleaseContext, early Oasis singles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsInReleaseContext Context triple: [Cloudburst, followsInReleaseContext, early Oasis singles]
-
A.
followsReleaseStrategyOf
Indicates that one entity adopts or adheres to the same release strategy or release management approach as another entity.
-
B.
followsInReleaseChronology
Indicates that one entity is released after another in a chronological sequence of releases.
-
C.
followsIn
Indicates that one entity comes after or succeeds another in a sequence, order, or progression.
-
D.
isReleasedInContextOf
chosen
Indicates that an entity is released or made available specifically within, or as part of, a particular context, situation, or framework.
-
E.
followUpRelease
Indicates that one release occurs subsequently as a continuation or update to a previous release.
- 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_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 27, 2026, 3:09 p.m.