Triple
T29957344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Harbour House |
E760937
|
entity |
| Predicate | hostedPerformancesBy |
P38415
|
FINISHED |
| Object | DJs |
—
|
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: DJs | Statement: [The Harbour House, hostedPerformancesBy, DJs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostedPerformancesBy Context triple: [The Harbour House, hostedPerformancesBy, DJs]
-
A.
presentsPerformancesBy
chosen
Indicates that one entity organizes or stages performances that feature or are carried out by another entity.
-
B.
laterPerformanceVenue
Indicates that a performance or event took place at this venue at a later time than another referenced performance or venue.
-
C.
hasLivePerformanceWith
Indicates that two or more entities participate together in the same live performance event.
-
D.
hasVenueFor
Indicates that one entity provides or serves as the location or setting where an event, activity, or function takes place for another entity.
-
E.
performsMusicIn
Indicates that an entity presents or plays music within a particular venue, event, or context.
- 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_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca204148190850a3dc325bc07b7 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 29, 2026, 6:27 p.m.