Triple
T38528141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zignia Live |
E923282
|
entity |
| Predicate | venuePromoted |
P134947
|
FINISHED |
| Object | Arena Monterrey |
—
|
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: Arena Monterrey | Statement: [Zignia Live, venuePromoted, Arena Monterrey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: venuePromoted Context triple: [Zignia Live, venuePromoted, Arena Monterrey]
-
A.
tourPromotion
Indicates a promotional relationship where an entity is being advertised, marketed, or highlighted as part of a tour or touring event.
-
B.
venueFlagship
Indicates that a venue serves as the primary or flagship location within a brand, organization, or chain.
-
C.
venueAssociatedWith
chosen
Indicates that there is a relevant connection or linkage between an event, activity, or entity and a particular venue or location.
-
D.
venueManaged
Indicates that one entity is responsible for operating, organizing, or overseeing the management of a particular venue.
-
E.
venue
Indicates the place or location where an event, activity, or interaction takes 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_69f76ea8f6348190a5c03fb6292bbee3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.