Triple
T23280322
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hajduk Split |
E588840
|
entity |
| Predicate | typeOfRivalryWithDinamoZagreb |
P29010
|
FINISHED |
| Object | long-standing |
—
|
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: long-standing | Statement: [Hajduk Split, typeOfRivalryWithDinamoZagreb, long-standing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfRivalryWithDinamoZagreb Context triple: [Hajduk Split, typeOfRivalryWithDinamoZagreb, long-standing]
-
A.
typeOfRivalry
chosen
Indicates a competitive or adversarial relationship between entities, specifying the particular kind or nature of rivalry that exists between them.
-
B.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
-
C.
associatedRivalry
Indicates a relationship where one entity is linked to another as its rival, competitor, or opposing counterpart.
-
D.
rivalryLevel
Indicates the degree or intensity of competitive opposition or conflict between two entities.
-
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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f19642b46481909fd455acd2155792 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:51 p.m.