Triple
T25600984
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eternal Derby of Bulgaria |
E641786
|
entity |
| Predicate | countryDerbyStatus |
P173193
|
FINISHED |
| Object | major football derby in Bulgaria |
—
|
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: major football derby in Bulgaria | Statement: [Eternal Derby of Bulgaria, countryDerbyStatus, major football derby in Bulgaria]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: countryDerbyStatus Context triple: [Eternal Derby of Bulgaria, countryDerbyStatus, major football derby in Bulgaria]
-
A.
countryOfRivalry
Indicates that one entity is a country with which another entity has a relationship of rivalry or adversarial competition.
-
B.
countryLeagueScope
Indicates that a league’s scope or coverage is defined at the level of a specific country.
-
C.
cityDerbyHosted
Indicates that a particular city served as the host location for a specified derby event.
-
D.
countryRivalClubs
Indicates that two sports clubs from the same country are considered rivals.
-
E.
homeMatchesCountry
Indicates that an entity’s home location is situated within the specified country.
- 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_69e75dc60d108190b7e2419e36b0134b |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f6b342499c8190b85009a3f0f179e4 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b2a31e008190aacef03c2ebe5787 |
completed | May 3, 2026, 2:27 a.m. |
Created at: April 21, 2026, 4:31 p.m.