Triple
T11722688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Latitude 38 Entertainment |
E278676
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | live events production company |
C19240
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: live events production company Context triple: [Latitude 38 Entertainment, instanceOf, live events production company]
-
A.
live event production company
chosen
A live event production company plans, coordinates, and executes all technical and creative aspects of concerts, conferences, festivals, and other in-person experiences to deliver seamless, engaging events.
-
B.
event producer
An event producer is an entity responsible for creating, organizing, and managing events by coordinating resources, logistics, and stakeholders to deliver a planned experience.
-
C.
management and production company
A management and production company is a business entity that represents and guides talent or projects while overseeing the development, financing, and execution of creative or commercial productions.
-
D.
live entertainment offering
A live entertainment offering is a scheduled in-person or real-time performance or event—such as a concert, play, comedy show, or sports game—presented to an audience for enjoyment and engagement.
-
E.
television production company
A television production company is an organization that develops, finances, and produces television content such as series, specials, and documentaries for broadcast, cable, or streaming platforms.
- F. None of above.
Provenance (1 batch)
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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:40 p.m.