Triple
T20124241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Arrivals |
E490702
|
entity |
| Predicate | livePerformanceReputation |
P71528
|
FINISHED |
| Object | energetic 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: energetic live shows | Statement: [The Arrivals, livePerformanceReputation, energetic live shows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livePerformanceReputation Context triple: [The Arrivals, livePerformanceReputation, energetic live shows]
-
A.
hasLivePerformanceReputation
chosen
Indicates that an entity is recognized or characterized by a particular reputation regarding the quality or nature of its live performances.
-
B.
venueReputation
Indicates the perceived quality or standing of a venue based on opinions, experiences, or evaluations associated with it.
-
C.
liveReputation
Indicates a dynamic, continuously updated assessment of an entity’s standing, trustworthiness, or performance based on recent or real-time information.
-
D.
livePerformanceFeature
Indicates that one entity is included or highlighted as a component of another entity’s live performance.
-
E.
livePerformanceStapleFor
Indicates that something (such as a song or piece) is regularly and prominently featured in another entity’s live 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667412b888190b43f7dd1ccdbad01 |
completed | April 20, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:30 p.m.