Triple
T6614182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Verde e Brancos |
E149306
|
entity |
| Predicate | clubSport |
P1907
|
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: [Verde e Brancos, clubSport, association football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clubSport Context triple: [Verde e Brancos, clubSport, association football]
-
A.
tenantSport
Indicates that a tenant participates in or is associated with a particular sport.
-
B.
club
Indicates that an entity is a member of, affiliated with, or participates in the activities of a particular club or organized group.
-
C.
sportCategory
chosen
Indicates that one entity is classified as a type or category of sport to which the other entity (typically a specific sport or sporting event) belongs.
-
D.
sportsAndRecreation
Indicates a relationship where an entity is associated with, involved in, or designated for sports or recreational activities.
-
E.
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.
- 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_69c687ebc680819094caf71faba2efe2 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6bdb88cc881908f35648c15a7dc85 |
completed | March 27, 2026, 5:26 p.m. |
| PD | Predicate disambiguation | batch_69c6ad007c1c8190af425f51011c7ad1 |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:57 p.m.