Triple
T26830467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | I'll See You Again |
E675485
|
entity |
| Predicate | performingArtsWork |
P176280
|
FINISHED |
| Object | Bitter Sweet |
—
|
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: Bitter Sweet | Statement: [I'll See You Again, performingArtsWork, Bitter Sweet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performingArtsWork Context triple: [I'll See You Again, performingArtsWork, Bitter Sweet]
-
A.
performingArtsWorkOf
chosen
Indicates that one entity is a performing arts work (such as a play, dance, or musical performance) created by or belonging to another entity.
-
B.
performingArtsDomain
Indicates that the subject operates within, is related to, or is characterized by the field of performing arts.
-
C.
performsMusicIn
Indicates that an entity presents or plays music within a particular venue, event, or context.
-
D.
performingArtRole
Indicates a role or function that an entity fulfills within the context of a performing arts activity or production.
-
E.
performances
Indicates that an entity stages, presents, or executes artistic or entertainment events for an audience.
- 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
Created at: April 27, 2026, 5:01 a.m.