Triple
T37082334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gas Pedal |
E918177
|
entity |
| Predicate | hasPopularityContext |
P42306
|
FINISHED |
| Object | radio play |
—
|
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: radio play | Statement: [Gas Pedal, hasPopularityContext, radio play]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPopularityContext Context triple: [Gas Pedal, hasPopularityContext, radio play]
-
A.
hasPopularityScope
Indicates that the popularity of an entity is evaluated or applicable within a specified scope, context, or audience.
-
B.
hasPopularityCharacteristic
Indicates that an entity possesses a particular attribute or quality related to its level or type of popularity.
-
C.
popularityContext
chosen
Indicates the situational or domain-specific setting in which something’s popularity or level of public favor is evaluated.
-
D.
hasPopularityInfluencedBy
Indicates that the popularity level of one entity is affected or shaped by another specified factor or entity.
-
E.
peakPopularity
Indicates the time or context in which something reaches its highest level of popularity relative to other times or contexts.
- 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_69f76e9952b88190a6fe01ba01476520 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffacdf9f5c8190baef0245edfe87fc |
completed | May 9, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69ffac5e86e08190a1e6da0840a237ad |
completed | May 9, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:14 p.m.