Triple
T10237369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Thessaloniki derby |
E243498
|
entity |
| Predicate | involvesCupMatches |
P92911
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Thessaloniki derby, involvesCupMatches, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesCupMatches Context triple: [Thessaloniki derby, involvesCupMatches, yes]
-
A.
cupCompetition
Indicates a competitive event or tournament, typically in a knockout or cup format, held between teams or individuals.
-
B.
hasDomesticCupRelation
Indicates a relationship between entities based on participation, achievement, or involvement in a domestic cup competition within a country’s sports structure.
-
C.
matchOf
Indicates that one entity is a specific match, counterpart, or corresponding instance of another entity within a defined context or set.
-
D.
hasCupTieEntry
Indicates that an entity has an associated entry or participation record in a cup-style competition or knockout tournament.
-
E.
qualificationMatchesPlayed
Indicates that the number of qualification matches associated with an entity has been played or completed.
- F. None of above. chosen
Provenance (4 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_69d381b0f97c819085c9b45799a5fb7c |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d23b620c8190b8a72d0eb0d16b93 |
completed | April 7, 2026, 9:45 a.m. |
| PD | Predicate disambiguation | batch_69d4d1e9798c8190b437d53d48554ba1 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d23a9c4c8190abece9e52879c479 |
completed | April 7, 2026, 9:45 a.m. |
Created at: April 6, 2026, 11:22 a.m.