Triple
T26550983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biancoscudati |
E671676
|
entity |
| Predicate | sportTypeOfAssociatedClub |
P142014
|
FINISHED |
| Object | association football |
—
|
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: association football | Statement: [Biancoscudati, sportTypeOfAssociatedClub, association football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sportTypeOfAssociatedClub Context triple: [Biancoscudati, sportTypeOfAssociatedClub, association football]
-
A.
associatedClubSport
chosen
Indicates that there is a relationship between a club and the sport with which it is connected or aligned.
-
B.
sportingAssociation
Indicates a formal relationship in which an organization serves as a governing, organizing, or affiliating body for sports activities, teams, or events.
-
C.
sportsAssociation
Indicates a formal relationship in which an entity is affiliated with, governed by, or participates under the auspices of a specific sports organization or governing body.
-
D.
tenantSport
Indicates that a tenant participates in or is associated with a particular sport.
-
E.
sportOfReferencedTeam
Indicates that the subject is the sport played by, or associated with, the referenced team.
- 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_69eeb32163f08190af5f81282738e27a |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 1:47 a.m.