Triple
T25793598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Say What! |
E649612
|
entity |
| Predicate | hasPerformerEra |
P148478
|
FINISHED |
| Object | late 20th century |
—
|
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: late 20th century | Statement: [Say What!, hasPerformerEra, late 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformerEra Context triple: [Say What!, hasPerformerEra, late 20th century]
-
A.
associatedWithArtistEra
Indicates a relationship where an artist is linked to a particular artistic era or period with which their work or influence is identified.
-
B.
hasLivePerformanceEra
chosen
Indicates that an entity is associated with a specific period or era characterized by its live performance activity.
-
C.
hasPerformerBirthYear
Indicates that a performer is associated with a specific year in which they were born.
-
D.
recordingArtistDebutEra
Indicates the time period or era during which an artist first debuted as a recording artist.
-
E.
isFromArtistDebutEra
Indicates that the item is associated with the period corresponding to the artist’s debut era, such as their first major releases or initial phase of their career.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 22, 2026, 6:01 a.m.