Triple
T16879163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fight the Power |
E421372
|
entity |
| Predicate | hasLivePerformancesAt |
P55120
|
FINISHED |
| Object | political rallies |
—
|
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: political rallies | Statement: [Fight the Power, hasLivePerformancesAt, political rallies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLivePerformancesAt Context triple: [Fight the Power, hasLivePerformancesAt, political rallies]
-
A.
hasLivePerformanceWith
Indicates that two or more entities participate together in the same live performance event.
-
B.
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.
-
C.
hasPerformedLiveIn
chosen
Indicates that an entity has given a live performance in a specified location or venue.
-
D.
hasLiveMusic
Indicates that a place or event features live musical performances as part of its offerings.
-
E.
hasFanPerformances
Indicates that an entity has associated performances created or carried out by fans.
- 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_69d889d470fc8190b4aec199636c0c56 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3b7f9aea0819090aef3c0c1ad349d |
completed | April 18, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69e32b90ec3c819099c51bb7baf2984c |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:29 a.m.