Triple
T13251497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ankara derby |
E315541
|
entity |
| Predicate | involvesCompetitionType |
P2440
|
FINISHED |
| Object | league matches |
—
|
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: league matches | Statement: [Ankara derby, involvesCompetitionType, league matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesCompetitionType Context triple: [Ankara derby, involvesCompetitionType, league matches]
-
A.
typeOfCompetition
chosen
Indicates the specific kind or category of competition in which an entity participates or is involved.
-
B.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
C.
associatedCompetitionType
Indicates that one entity is linked to or involved with a particular type or category of competition.
-
D.
includesCompetition
Indicates that one entity contains, features, or encompasses a competition as part of its scope or content.
-
E.
overseesCompetitionType
Indicates that one entity has responsibility for supervising, managing, or regulating a particular type or category of competition.
- 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_69d806b1072881909e46bd212259c5f0 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f60911081909fa346a054f76c9f |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:24 p.m.