Triple
T1921745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Springsteen on Broadway |
E40138
|
entity |
| Predicate | marketingMethod |
P9029
|
FINISHED |
| Object | ticket lottery |
—
|
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: ticket lottery | Statement: [Springsteen on Broadway, marketingMethod, ticket lottery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketingMethod Context triple: [Springsteen on Broadway, marketingMethod, ticket lottery]
-
A.
campaignMethod
chosen
Indicates the method or approach used to conduct or deliver a campaign.
-
B.
marketingUse
Indicates that something is used for marketing purposes, such as promotion, advertising, or brand communication.
-
C.
marketingAs
Indicates that one entity is being presented, promoted, or branded to others as if it were another specified entity, role, or category.
-
D.
marketingStrategy
Indicates the approach or plan an entity uses to promote, position, and sell its products or services to a target audience.
-
E.
marketingModel
Indicates a relationship where an entity uses or is associated with a specific marketing model, framework, or strategy to guide promotional or market-related decisions.
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb233011881908736523d36f01b0c |
completed | March 7, 2026, 5:05 a.m. |
| PD | Predicate disambiguation | batch_69abafed2ab481908920334e77b1021b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.