Triple
T32407278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beyoncé’s 2018 Coachella performance |
E828116
|
entity |
| Predicate | rehearsalPeriod |
P24075
|
FINISHED |
| Object | approximately eight months |
—
|
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: approximately eight months | Statement: [Beyoncé’s 2018 Coachella performance, rehearsalPeriod, approximately eight months]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rehearsalPeriod Context triple: [Beyoncé’s 2018 Coachella performance, rehearsalPeriod, approximately eight months]
-
A.
preparationPeriod
chosen
Indicates the time span allocated before an event or action during which necessary preparations are made.
-
B.
hasRehearsalSpaces
Indicates that an entity provides or contains designated spaces specifically intended for rehearsing activities or performances.
-
C.
trainingPeriod
Indicates the duration or phase during which training or instruction is formally conducted.
-
D.
hasRehearsalFormat
Indicates that an entity is associated with a particular format or structure in which a rehearsal is conducted.
-
E.
reorganizationPeriod
Indicates the time span during which a structural or organizational change is planned, underway, or in effect.
- 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_69f34919f300819092b541c6277cd68a |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c24ca0f08190a5b2c1d32205eaee |
completed | May 3, 2026, 3:34 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:53 a.m.