Triple
T2701235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thunderbitch |
E59231
|
entity |
| Predicate | hasPerformanceStyle |
P13362
|
FINISHED |
| Object | high-energy live shows |
—
|
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: high-energy live shows | Statement: [Thunderbitch, hasPerformanceStyle, high-energy live shows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformanceStyle Context triple: [Thunderbitch, hasPerformanceStyle, high-energy live shows]
-
A.
hasPerformanceConvention
Indicates that there is an agreed-upon set of rules, norms, or standards governing how a particular performance or activity should be carried out.
-
B.
hasStyle
Indicates that an entity possesses, exhibits, or is characterized by a particular style or manner.
-
C.
performanceStyle
chosen
Indicates the manner or style in which an action, work, or performance is carried out or presented.
-
D.
hasSystemStyle
Indicates that one entity is associated with, or characterized by, a particular system-defined style of another entity.
-
E.
hasContractStyle
Indicates that one entity is associated with or characterized by a particular contract style or contractual format.
- 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_69ab4ac66bc88190b9e4afa5fc843f72 |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda4c8d34819094f5e4cbc5a4bb9b |
completed | March 7, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69abd82062988190b4292f242ad70b2c |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.