Triple
T5151331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FC Pirin Blagoevgrad |
E116199
|
entity |
| Predicate | playsInAssociationFootball |
P39137
|
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: [FC Pirin Blagoevgrad, playsInAssociationFootball, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsInAssociationFootball Context triple: [FC Pirin Blagoevgrad, playsInAssociationFootball, yes]
-
A.
playedAssociationFootball
Indicates that an entity has participated in playing the sport of association football (soccer).
-
B.
basedInSport
chosen
Indicates that an entity (such as a team, organization, or person) is primarily associated with or operates within a particular sport.
-
C.
leaguePlayedIn
Indicates that a sports team or player has participated in competitions within a particular league.
-
D.
associatedWithFootballClub
Indicates that there is a relationship of affiliation or connection between an entity and a football club.
-
E.
leagueUsedFor
Indicates that a particular league is utilized as the context, setting, or organizing framework for some activity, event, or 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_69bd445d94788190b72e2cc563120995 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd79c1354c81908176703b4853c1a4 |
completed | March 20, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69bd77b0fbb88190851e2d7ae1bdcc09 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:44 p.m.