Triple
T29957562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Essence |
E760945
|
entity |
| Predicate | hostedActivity |
P2777
|
FINISHED |
| Object | DJ sets |
—
|
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: DJ sets | Statement: [The Essence, hostedActivity, DJ sets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostedActivity Context triple: [The Essence, hostedActivity, DJ sets]
-
A.
hostsEvent
Indicates that an entity organizes and provides the venue or setting for an event to take place.
-
B.
hostedAttraction
Indicates that an entity served as the venue or location where a particular attraction, event, or feature was presented or took place.
-
C.
hostedDuring
Indicates that one entity hosted, organized, or held another entity (such as an event or activity) within a specified time period.
-
D.
hosted
chosen
Indicates that one entity organized and provided the venue or platform for an event, activity, or presence involving another entity.
-
E.
hostedEventAreaFor
Indicates that a particular area or location served as the venue or physical space where an event was hosted or took place.
- 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_69f22466327481908ba6db916837bece |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 29, 2026, 6:27 p.m.