Triple
T28959833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ultra Enterprises Inc. |
E731865
|
entity |
| Predicate | operatesEventsIn |
P152375
|
FINISHED |
| Object | multiple cities worldwide |
—
|
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: multiple cities worldwide | Statement: [Ultra Enterprises Inc., operatesEventsIn, multiple cities worldwide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesEventsIn Context triple: [Ultra Enterprises Inc., operatesEventsIn, multiple cities worldwide]
-
A.
operatesFestival
Indicates that one entity manages and runs the organization or execution of a festival for another entity or in a particular context.
-
B.
operatesVenue
Indicates that one entity manages and runs the day-to-day operations of a particular venue.
-
C.
eventManagement
Indicates the organization, coordination, and oversight of all activities and resources involved in planning and executing an event.
-
D.
alsoHostsEventsIn
chosen
Indicates that an entity, in addition to its primary location or context, serves as a venue or place where events are held in another specified location.
-
E.
hasEventHostingCapability
Indicates that an entity possesses the ability or resources to host or organize events.
- 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_69f043ee242c8190b063248b417c5a69 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
Created at: April 28, 2026, 8:49 a.m.