Triple
T21020853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Five of Argentine football |
E517801
|
entity |
| Predicate | hasRivalryStructure |
P91581
|
FINISHED |
| Object | Boca Juniors vs River Plate |
—
|
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: Boca Juniors vs River Plate | Statement: [Big Five of Argentine football, hasRivalryStructure, Boca Juniors vs River Plate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRivalryStructure Context triple: [Big Five of Argentine football, hasRivalryStructure, Boca Juniors vs River Plate]
-
A.
hasRivalryRoot
Indicates that a rivalry relationship originates from, or is fundamentally based on, a particular source, cause, or underlying factor.
-
B.
hasRivalryFormat
chosen
Indicates that there is a specific structure, set of rules, or format that defines how a rivalry between entities is conducted or organized.
-
C.
hasRivalryAspect
Indicates that there exists a competitive or adversarial relationship or dimension between entities.
-
D.
hasRivalryContext
Indicates that there exists a competitive or adversarial relationship between entities within a specific situational or contextual framework.
-
E.
hasRivalrySeries
Indicates a recurring competitive relationship or series of contests held between two entities.
- 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_69e0b50262b081909bc488937145eb73 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e6fc5c905c8190ba2f9f82b6cd1648 |
completed | April 21, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69e5dbf274ac81909bbf245627dc8fdc |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:54 p.m.