Triple
T22657177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cape Town derby |
E559257
|
entity |
| Predicate | rivalryScope |
P29010
|
FINISHED |
| Object | intra-city rivalry |
—
|
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: intra-city rivalry | Statement: [Cape Town derby, rivalryScope, intra-city rivalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalryScope Context triple: [Cape Town derby, rivalryScope, intra-city rivalry]
-
A.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
-
B.
rivalryFocus
Indicates a relationship in which one entity is the primary target or center of another entity’s competitive or adversarial rivalry.
-
C.
rivalryLevel
Indicates the degree or intensity of competitive opposition or conflict between two entities.
-
D.
typeOfRivalry
chosen
Indicates a competitive or adversarial relationship between entities, specifying the particular kind or nature of rivalry that exists between them.
-
E.
rivalryStatus
Indicates a competitive or adversarial relationship between entities, often involving ongoing opposition or contention.
- 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_69e245489dd88190b1f674acf61c8769 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1765c62bc8190b3fcde76d6b6dfb6 |
completed | April 29, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:06 p.m.