Triple
T33699600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enjoy |
E863416
|
entity |
| Predicate | isPerformedLive |
P125875
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Enjoy, isPerformedLive, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPerformedLive Context triple: [Enjoy, isPerformedLive, true]
-
A.
isPerformedLiveBy
Indicates that an action, event, or performance occurs in real time in front of an audience and is carried out by the specified entity.
-
B.
hasLivePerformanceStatus
Indicates whether an entity’s live performance is occurring, scheduled, completed, or otherwise characterized by a specific performance status.
-
C.
hasPerformedLiveIn
Indicates that an entity has given a live performance in a specified location or venue.
-
D.
isLive
chosen
Indicates that an entity is currently broadcasting or occurring in real time, as opposed to being pre-recorded or inactive.
-
E.
isFrequentlyPerformedLive
Indicates that an action or event regularly occurs in live, in-person or real-time performances.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fa8bd50481908fd1a9b5406a5855 |
completed | May 3, 2026, 7:34 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:43 a.m.