Triple
T37418384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cola Wars |
E929780
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | marketing rivalry |
C21112
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: marketing rivalry Context triple: [Cola Wars, instanceOf, marketing rivalry]
-
A.
commercial rivalry
chosen
Commercial rivalry is the competitive relationship between businesses striving to outperform each other in market share, profitability, and customer loyalty through strategies such as pricing, innovation, marketing, and differentiation.
-
B.
angling competition
An angling competition is an organized event in which participants fish within set rules and time limits, aiming to catch the largest or most fish to win prizes or recognition.
-
C.
competition
Competition is a structured interaction in which individuals or groups strive against one another to achieve a goal that cannot be fully shared, often to determine relative superiority or allocate limited resources.
-
D.
international competition
An international competition is a structured event in which individuals or teams from multiple countries compete under standardized rules to determine relative excellence in a specific field or activity.
-
E.
competition policy
Competition policy is the set of laws, regulations, and enforcement practices designed to promote fair market competition, prevent anti-competitive behavior, and protect consumer welfare.
- F. None of above.
Provenance (1 batch)
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_69f76ebde49481908566cd96b37ccc84 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.