Triple
T29838320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Ibiza |
E757714
|
entity |
| Predicate | notablePartyBrand |
P60713
|
FINISHED |
| Object | Carl Cox Music Is Revolution |
E731876
|
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: Carl Cox Music Is Revolution | Statement: [Space Ibiza, notablePartyBrand, Carl Cox Music Is Revolution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePartyBrand Context triple: [Space Ibiza, notablePartyBrand, Carl Cox Music Is Revolution]
-
A.
notableParty
Indicates that an entity is a significant or noteworthy participant in an event, activity, or relationship.
-
B.
notableBrandElement
chosen
Indicates that one entity is a significant or distinguishing brand-related feature, component, or asset of another entity.
-
C.
notablePartner
Indicates that two entities are or have been significant partners, typically in a prominent or noteworthy personal or professional relationship.
-
D.
notableManufacturer
Indicates that an entity is a well-known or prominent producer or maker of another entity.
-
E.
popularBrand
Indicates that a brand is widely liked, recognized, or frequently chosen by many people.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a26e60951048190a16947cecbb04790 |
completed | June 8, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 5:38 p.m.