Triple
T29647685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandalay Beach |
E756047
|
entity |
| Predicate | hasMusicEvents |
P13977
|
FINISHED |
| Object | concerts on beachside stage |
—
|
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: concerts on beachside stage | Statement: [Mandalay Beach, hasMusicEvents, concerts on beachside stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMusicEvents Context triple: [Mandalay Beach, hasMusicEvents, concerts on beachside stage]
-
A.
hasLiveMusic
chosen
Indicates that a place or event features live musical performances as part of its offerings.
-
B.
hasCulturalEvent
Indicates that a cultural event (such as a festival, performance, or exhibition) takes place in, is associated with, or is hosted by a given entity.
-
C.
hasLivePerformanceWith
Indicates that two or more entities participate together in the same live performance event.
-
D.
hasPublicEventsIn
Indicates that an entity organizes or holds public events within a specified location or context.
-
E.
hasFestival
Indicates that a location, community, or entity hosts or holds a festival or celebratory event.
- 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_69f0ef89d2c88190a6d0d5116ccd7cc9 |
completed | April 28, 2026, 5:34 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: April 28, 2026, 6:50 p.m.