Triple
T437196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harris Theater for Music and Dance |
E10034
|
entity |
| Predicate | venueUse |
P8643
|
FINISHED |
| Object | live performance |
—
|
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: live performance | Statement: [Harris Theater for Music and Dance, venueUse, live performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: venueUse Context triple: [Harris Theater for Music and Dance, venueUse, live performance]
-
A.
venue
Indicates the place or location where an event, activity, or interaction takes place.
-
B.
venueConcept
chosen
Indicates a relationship where a venue is associated with, characterized by, or defined in terms of a particular concept or thematic idea.
-
C.
eventUse
Indicates that an event involves the use or utilization of a particular entity (e.g., a resource, tool, or method) as part of its occurrence.
-
D.
servesVenue
Indicates that an entity provides services or functions in support of a particular venue.
-
E.
reservationSystem
Indicates a system or process that manages the creation, modification, and tracking of reservations or bookings between parties.
- 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_69a2e8465ef481909655c681b01e2986 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2ef26bb78819089b3b5dac0330619 |
completed | Feb. 28, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69a2eddb98e081909efcf9f0a955a908 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.