Triple
T10102963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Torneio Rio-São Paulo |
E216246
|
entity |
| Predicate | mainRivalryShowcased |
P8277
|
FINISHED |
| Object | Rio de Janeiro vs São Paulo clubs |
—
|
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: Rio de Janeiro vs São Paulo clubs | Statement: [Torneio Rio-São Paulo, mainRivalryShowcased, Rio de Janeiro vs São Paulo clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainRivalryShowcased Context triple: [Torneio Rio-São Paulo, mainRivalryShowcased, Rio de Janeiro vs São Paulo clubs]
-
A.
isMajorRivalryFor
Indicates that one entity is a primary or highly significant competitor or adversary to another, often characterized by ongoing, notable, or intense rivalry.
-
B.
hasRivalryAspect
chosen
Indicates that there exists a competitive or adversarial relationship or dimension between entities.
-
C.
associatedRivalry
Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
-
D.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
-
E.
hasRivalryEmotion
Indicates that one entity feels rivalry-based emotions, such as competitive tension or antagonistic comparison, toward another entity.
- 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_69ca83d039f08190b9d10363221c69fb |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd09af07c819099774af46ebf62d7 |
completed | April 2, 2026, 2:12 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 9:02 p.m.