Triple
T34139840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cole World Tour |
E875685
|
entity |
| Predicate | followsReleaseOf |
P126350
|
FINISHED |
| Object | Cole World: The Sideline Story |
—
|
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: Cole World: The Sideline Story | Statement: [Cole World Tour, followsReleaseOf, Cole World: The Sideline Story]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsReleaseOf Context triple: [Cole World Tour, followsReleaseOf, Cole World: The Sideline Story]
-
A.
followsReleaseType
Indicates that one release adheres to, or is categorized under, a specified type or pattern of release.
-
B.
followsReleaseStrategyOf
Indicates that one entity adopts or adheres to the same release strategy or release management approach as another entity.
-
C.
followsInReleaseChronology
Indicates that one entity is released after another in a chronological sequence of releases.
-
D.
followUpRelease
Indicates that one release occurs subsequently as a continuation or update to a previous release.
-
E.
releasedFollowing
chosen
Indicates that one entity was released after another entity, in a subsequent or later release order.
- 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_69f349aaeef08190a20e72a3fdeb7052 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69feb5e66224819083b87c3707a5a5e0 |
completed | May 9, 2026, 4:19 a.m. |
| PD | Predicate disambiguation | batch_69feb3bd700c8190991ed200cd3c04db |
completed | May 9, 2026, 4:10 a.m. |
Created at: May 1, 2026, 1:53 a.m.