Triple
T6615393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 11 O’Clock Tick Tock |
E149336
|
entity |
| Predicate | hasLivePerformanceReputation |
P71528
|
FINISHED |
| Object | fan favorite |
—
|
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: fan favorite | Statement: [11 O’Clock Tick Tock, hasLivePerformanceReputation, fan favorite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLivePerformanceReputation Context triple: [11 O’Clock Tick Tock, hasLivePerformanceReputation, fan favorite]
-
A.
hasNotableLivePerformancesBy
Indicates that an entity (such as a work, event, or venue) is associated with notable live performances given by a specified performer or group.
-
B.
hasPerformedLiveIn
Indicates that an entity has given a live performance in a specified location or venue.
-
C.
livePerformanceFeature
Indicates that one entity is included or highlighted as a component of another entity’s live performance.
-
D.
hasLivePerformanceTradition
Indicates that there exists an established custom or practice of performing the subject live, typically before an audience.
-
E.
hasFanPerformances
Indicates that an entity has associated performances created or carried out by fans.
- F. None of above. chosen
Provenance (4 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_69c687ebc680819094caf71faba2efe2 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6bdb88cc881908f35648c15a7dc85 |
completed | March 27, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69c6ad007c1c8190af425f51011c7ad1 |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6bdb76ec48190b59d576170970cc9 |
completed | March 27, 2026, 5:26 p.m. |
Created at: March 27, 2026, 1:57 p.m.