Triple
T31302651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lover Fest |
E798248
|
entity |
| Predicate | includedPlannedShow |
P81597
|
FINISHED |
| Object | Lover Fest West |
—
|
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: Lover Fest West | Statement: [Lover Fest, includedPlannedShow, Lover Fest West]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedPlannedShow Context triple: [Lover Fest, includedPlannedShow, Lover Fest West]
-
A.
includesShow
chosen
Indicates that one entity contains or features a particular show as part of its content or offerings.
-
B.
plannedTheater
Indicates that an entity has scheduled or arranged for a theater-related event or activity to take place.
-
C.
includedPlannedMember
Indicates that an entity has been designated or scheduled to be part of a group, set, or collection as a planned member.
-
D.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
-
E.
associatedShow
Indicates a relationship where one entity is linked or connected to a particular show (e.g., as its subject, source, or related program).
- 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_69f224e0bd4c8190aab9b29a73f7aa3c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a0115fb84448190b8b67a5ace7b289a |
completed | May 10, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_6a0114ef60a081908f8db7868cf29b2f |
completed | May 10, 2026, 11:29 p.m. |
Created at: April 29, 2026, 9:14 p.m.