Triple
T32338548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Randy |
E826241
|
entity |
| Predicate | hadPeakPopularityPeriod |
P105129
|
FINISHED |
| Object | mid-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: mid-20th century | Statement: [Randy, hadPeakPopularityPeriod, mid-20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadPeakPopularityPeriod Context triple: [Randy, hadPeakPopularityPeriod, mid-20th century]
-
A.
hadPeakInfluencePeriod
Indicates the time span during which an entity exerted its greatest or most significant influence.
-
B.
achievedPopularityIn
Indicates that an entity became popular or widely recognized within a specified place, group, or context.
-
C.
notablePopularityPeriod
chosen
Indicates the time span during which something was especially popular or widely recognized.
-
D.
popularInPeriod
Indicates that something is widely liked, used, or influential during a specified time period.
-
E.
timePeriodOfRiseInPopularity
Indicates the time span during which something became increasingly popular or widely favored.
- 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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be1c950c8190afe0ba37c1704c29 |
completed | May 3, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69f6b633e0c88190a727bb7d2751e2d5 |
completed | May 3, 2026, 2:43 a.m. |
Created at: May 1, 2026, 12:48 a.m.