Triple
T23547062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bigger Business (remix) |
E577926
|
entity |
| Predicate | hasRemixVersionOf |
P118697
|
FINISHED |
| Object | Bigger Business |
—
|
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: Bigger Business | Statement: [Bigger Business (remix), hasRemixVersionOf, Bigger Business]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRemixVersionOf Context triple: [Bigger Business (remix), hasRemixVersionOf, Bigger Business]
-
A.
hasRemix
Indicates that one creative work is a remix version derived from or based on another work.
-
B.
hasRemixVariant
chosen
Indicates that one entity is a remix version or reworked variant of another entity.
-
C.
hasRemixed
Indicates that one entity has created a new version or adaptation of another entity by remixing it.
-
D.
hasRemixRelationshipWith
Indicates that one creative work is a remix, reworked version, or derived adaptation of another work.
-
E.
hasRemixOrCovers
Indicates that one creative work is a remix or cover version of another work.
- 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_69e245fa93448190919cb04534560542 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aecb567c8190a54d2c3b63282af5 |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:11 p.m.