Triple
T5869850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stuffed Crust Pizza |
E130486
|
entity |
| Predicate | wasPopularizedIn |
P21730
|
FINISHED |
| Object | 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: 1990s | Statement: [Stuffed Crust Pizza, wasPopularizedIn, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasPopularizedIn Context triple: [Stuffed Crust Pizza, wasPopularizedIn, 1990s]
-
A.
popularizedIn
Indicates that something became widely known, accepted, or fashionable within a particular place, time period, or context.
-
B.
popularizedBy
Indicates that something became widely known, accepted, or fashionable as a result of the influence or actions of a particular agent.
-
C.
hasEnduringPopularityOn
Indicates that something continues to be widely liked, used, or appreciated on a particular platform, medium, or context over an extended period of time.
-
D.
decadeOfPopularization
chosen
Indicates the decade during which something became widely known, used, or popular.
-
E.
firstWidelyUsedFor
Indicates that something was the earliest instance to be broadly adopted or commonly used for a particular purpose or application.
- 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_69c0085047dc8190af24e311edad3c07 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ffaef081909faaa7f420a3b9b7 |
completed | March 22, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69c03347e51c81909053bcf34e3b88ab |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:56 p.m.