Triple
T34330982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PFC Ludogorets Razgrad |
E881005
|
entity |
| Predicate | UEFAMemberAssociation |
P67743
|
FINISHED |
| Object | Bulgarian Football Union |
—
|
NE NERFINISHED |
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: Bulgarian Football Union | Statement: [PFC Ludogorets Razgrad, UEFAMemberAssociation, Bulgarian Football Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: UEFAMemberAssociation Context triple: [PFC Ludogorets Razgrad, UEFAMemberAssociation, Bulgarian Football Union]
-
A.
UEFAMembership
chosen
Indicates that an entity holds membership or affiliation status within the UEFA organization.
-
B.
UNMembershipSupport
Indicates support for a country’s admission to, or continued membership in, the United Nations.
-
C.
UEFAMembershipSince
Indicates that an entity has been a member of UEFA starting from a specified date or point in time.
-
D.
UNMembershipContext
Indicates the relationship between an entity and its status, role, or circumstances of participation within the context of United Nations membership.
-
E.
fifaAffiliationOfAssociation
Indicates that a football association is officially affiliated with or recognized by FIFA.
- 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_69f349ba96a08190b94887bae2d8ee49 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f717836f0c8190b4a397bbac37dd09 |
completed | May 3, 2026, 9:38 a.m. |
| PD | Predicate disambiguation | batch_69f7127a2ff08190b77d00963c9df621 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:58 a.m.