Triple
T28295797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Monqui Presents |
E713565
|
entity |
| Predicate | operatesInVenue |
P5307
|
FINISHED |
| Object | Wonder Ballroom |
—
|
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: Wonder Ballroom | Statement: [Monqui Presents, operatesInVenue, Wonder Ballroom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesInVenue Context triple: [Monqui Presents, operatesInVenue, Wonder Ballroom]
-
A.
operatesVenue
chosen
Indicates that one entity manages and runs the day-to-day operations of a particular venue.
-
B.
locatedInOperatedVenue
Indicates that an entity is situated within a venue that is managed or operated by a specified agent or organization.
-
C.
operatesVenueInCity
Indicates that an entity operates or manages a venue located within a specified city.
-
D.
locatedInVenueType
Indicates that an entity is situated within or associated with a venue of a specific type (e.g., stadium, theater, restaurant).
-
E.
isRegularVenueFor
Indicates that a location is commonly or routinely used as the venue for a particular event, activity, or entity’s gatherings.
- 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_69efb524ab688190a1ce7ee7c9520932 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fe86cad5108190b0164b8bc6fc23ea |
completed | May 9, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69fe83c0c9888190b6fc40c7f727b569 |
completed | May 9, 2026, 12:45 a.m. |
Created at: April 27, 2026, 11:32 p.m.