Triple
T23900495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Placard |
E601028
|
entity |
| Predicate | majorSponsorOf |
P1807
|
FINISHED |
| Object | Portuguese 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: Portuguese football | Statement: [Placard, majorSponsorOf, Portuguese football]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorSponsorOf Context triple: [Placard, majorSponsorOf, Portuguese football]
-
A.
sponsorshipName
Indicates the name or title associated with a sponsorship relationship between entities.
-
B.
sponsors
chosen
Indicates that one entity provides financial or material support to another, often in exchange for association, promotion, or fulfillment of certain activities or goals.
-
C.
sponsorOfStadiumName
Indicates that an entity serves as the naming-rights sponsor for a particular stadium.
-
D.
sponsorshipBrand
Indicates that one entity serves as a sponsoring brand for another entity, typically providing support, funding, or endorsement.
-
E.
sponsoringOrganizationType
Indicates the kind or category of organization that provides sponsorship or support in the described relationship or activity.
- 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cdddca088190b6c26df984a143ad |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:26 p.m.