Triple
T5556308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Croatia and Serbia |
E145650
|
entity |
| Predicate | shareSportRivalryIn |
P60585
|
FINISHED |
| Object | football |
—
|
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: football | Statement: [Croatia and Serbia, shareSportRivalryIn, football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareSportRivalryIn Context triple: [Croatia and Serbia, shareSportRivalryIn, football]
-
A.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
-
B.
rivalLeague
Indicates that two leagues are in competition with each other, typically vying for similar audiences, resources, or status.
-
C.
divisionRivalry
Indicates a competitive or adversarial relationship between entities that belong to the same division or subgroup within a larger organization or system.
-
D.
hasRivalrySport
chosen
Indicates a competitive relationship in which two entities are rivals specifically within the context of a sport or sporting activity.
-
E.
sharesArenaWith
Indicates that two entities use or occupy the same arena as a common venue or location.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01ffc5e7c81908e1c454d3bfd357b |
completed | March 22, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.