Triple
T33313978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kitrinomavroi supporters |
E852961
|
entity |
| Predicate | cityDerbies |
P169498
|
FINISHED |
| Object | Thessaloniki football derbies |
—
|
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: Thessaloniki football derbies | Statement: [Kitrinomavroi supporters, cityDerbies, Thessaloniki football derbies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityDerbies Context triple: [Kitrinomavroi supporters, cityDerbies, Thessaloniki football derbies]
-
A.
cityDerby
Indicates a competitive or rivalry relationship between two cities, often in sports or similar local contests.
-
B.
cityDerbyName
Indicates that a city is known by a particular derby (rivalry match) name.
-
C.
cityDerbyHosted
Indicates that a particular city served as the host location for a specified derby event.
-
D.
intraCityDerby
chosen
Indicates a competitive match or rivalry that takes place between teams from the same city.
-
E.
cityRivalry
Indicates a competitive or adversarial relationship that exists between two cities, often involving sports, economics, culture, or historical tensions.
- 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_69f349679fd8819093b9b40e989440e3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:33 a.m.