Triple
T16555401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big beat |
E402186
|
entity |
| Predicate | gainedProminenceInPeriod |
P105129
|
FINISHED |
| Object | mid 1990s |
—
|
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: mid 1990s | Statement: [Big beat, gainedProminenceInPeriod, mid 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gainedProminenceInPeriod Context triple: [Big beat, gainedProminenceInPeriod, mid 1990s]
-
A.
gainedProminenceFor
Indicates that an entity became widely recognized or notable specifically because of another entity, action, or achievement.
-
B.
notablePopularityPeriod
chosen
Indicates the time span during which something was especially popular or widely recognized.
-
C.
wasProminentIn
Indicates that an entity was notably active, influential, or widely recognized within a particular field, context, or time period.
-
D.
flourishedDuring
Indicates that an entity was active, thriving, or at its peak during a specified time period or era.
-
E.
hadPeakInfluencePeriod
Indicates the time span during which an entity exerted its greatest or most significant influence.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fc887e881909607653df7fe71be |
completed | April 18, 2026, 9:32 a.m. |
| PD | Predicate disambiguation | batch_69e296a47b7481909d9958158510c806 |
completed | April 17, 2026, 8:23 p.m. |
Created at: April 10, 2026, 5:15 a.m.