Triple
T24515918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clássico (Porto vs Sporting) |
E606368
|
entity |
| Predicate | rivalryDimension |
P43969
|
FINISHED |
| Object | sporting success |
—
|
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: sporting success | Statement: [Clássico (Porto vs Sporting), rivalryDimension, sporting success]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rivalryDimension Context triple: [Clássico (Porto vs Sporting), rivalryDimension, sporting success]
-
A.
rivalryBasis
chosen
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
-
B.
rivalryLevel
Indicates the degree or intensity of competitive opposition or conflict between two entities.
-
C.
typeOfRivalry
Indicates a competitive or adversarial relationship between entities, specifying the particular kind or nature of rivalry that exists between them.
-
D.
rivalryFocus
Indicates a relationship in which one entity is the primary target or center of another entity’s competitive or adversarial rivalry.
-
E.
rivalryName
Indicates that a specific name or label is assigned to a rivalry relationship 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_69e2c4c725148190a4e41577c5cb409c |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2a9d912e88190bc39c05a9d7f407e |
completed | April 30, 2026, 1:01 a.m. |
| PD | Predicate disambiguation | batch_69f2a6a4580481908fddc385f5262f95 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:24 a.m.