Triple
T1332139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2005 U.S. Open Cup |
E28665
|
entity |
| Predicate | includesClubs |
P18795
|
FINISHED |
| Object | professional clubs |
—
|
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: professional clubs | Statement: [2005 U.S. Open Cup, includesClubs, professional clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesClubs Context triple: [2005 U.S. Open Cup, includesClubs, professional clubs]
-
A.
eligibleClubs
Indicates that certain clubs meet the required criteria or conditions to qualify for a specified status, activity, or benefit.
-
B.
includesAmateurClubs
Indicates that something (such as an organization, competition, or structure) contains or encompasses amateur-level clubs as part of it.
-
C.
involvesClub
Indicates that an action, event, or relationship includes or is associated with a specific club as a participating entity.
-
D.
supportsClubInLeague
Indicates that one entity provides backing or sponsorship for a club participating in a particular league.
-
E.
memberClubsType
chosen
Indicates that an entity is associated as a member with clubs of a specified type or category.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1e7f1388190a6e4eb65a7997380 |
completed | March 1, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69a4beef6a188190996f8775bdda8f6c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.