Triple
T30473730
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | No, Not Much |
E775381
|
entity |
| Predicate | originallyPopularizedIn |
P2352
|
FINISHED |
| Object | 1950s |
—
|
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: 1950s | Statement: [No, Not Much, originallyPopularizedIn, 1950s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originallyPopularizedIn Context triple: [No, Not Much, originallyPopularizedIn, 1950s]
-
A.
popularizedIn
chosen
Indicates that something became widely known, accepted, or fashionable within a particular place, time period, or context.
-
B.
popularizedOn
Indicates that something became widely known, accepted, or fashionable through a particular platform, medium, or context.
-
C.
popularizedInEnglishBy
Indicates that one entity is responsible for making another entity widely known or commonly used within the English language context.
-
D.
popularizedBy
Indicates that something became widely known, accepted, or fashionable as a result of the influence or actions of a particular agent.
-
E.
popularizedSince
Indicates that one entity has become widely known, accepted, or influential starting from a specified time or period.
- 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_69f22497341481909c21ba329fadaa6b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a004b6ad4248190b402a0d01b0ebf83 |
completed | May 10, 2026, 9:10 a.m. |
| PD | Predicate disambiguation | batch_6a004ae736b881908a0efed8f63f982e |
completed | May 10, 2026, 9:07 a.m. |
Created at: April 29, 2026, 8:11 p.m.