Triple
T31930348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaleidoscope |
E815227
|
entity |
| Predicate | includesAlternateVersionOf |
P201927
|
FINISHED |
| Object | Something Just Like This |
E234242
|
NE 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: Something Just Like This | Statement: [Kaleidoscope, includesAlternateVersionOf, Something Just Like This]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesAlternateVersionOf Context triple: [Kaleidoscope, includesAlternateVersionOf, Something Just Like This]
-
A.
isAlternativeTo
Indicates that one entity can serve as a substitute or different option in place of another.
-
B.
isVersionOf
Indicates that one entity is a particular version, edition, or variant derived from another entity.
-
C.
hasAlternateEditionISBN
Indicates that one edition of a work is linked to another edition of the same work via its alternate ISBN.
-
D.
hasRemixOrAlternateVersions
chosen
Indicates that an original work has one or more remix, alternate, or variant versions derived from it.
-
E.
hasAlternativeRadioVersionWith
Indicates that one audio track has a corresponding alternative version specifically edited or mixed for radio play.
- F. None of above.
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_69f348f3035c81908558e2339955abb3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a019b8995dc819088727aa023beadce |
completed | May 11, 2026, 9:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2e8a3abaa48190b640131399e466c3 |
completed | June 14, 2026, 11:02 a.m. |
| PD | Predicate disambiguation | batch_6a01961bb748819096a941f1b5443908 |
completed | May 11, 2026, 8:40 a.m. |
Created at: May 1, 2026, 12:04 a.m.