Triple
T24344824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dallas–Fort Worth vs. Houston |
E613610
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural rivalry |
C37431
|
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: cultural rivalry Context triple: [Dallas–Fort Worth vs. Houston, instanceOf, cultural rivalry]
-
A.
regional rivalry
chosen
Regional rivalry is a competitive and often tense relationship between neighboring areas or countries, driven by historical, cultural, economic, or political differences as they vie for influence, resources, or prestige.
-
B.
sports rivalry
A sports rivalry is a competitive relationship between teams, athletes, or fan bases characterized by repeated contests, heightened emotions, and historical or cultural significance that intensifies their matchups.
-
C.
cultural conflict
Cultural conflict is a clash between groups with differing values, beliefs, norms, or practices that leads to tension, misunderstanding, or struggle over identity, power, or resources.
-
D.
dynastic rivalry
Dynastic rivalry is the sustained political, military, and familial competition between ruling houses or lineages for supremacy, legitimacy, and control over territories or thrones.
-
E.
ritual competition
A ritual competition is a structured, often symbolic contest embedded in cultural or religious practice, where participants follow prescribed rules and performances to affirm social values, identities, or hierarchies.
- 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_69e2d7dcc5a08190b53691130d56cbc4 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 1:58 a.m.