Triple
T1125748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Open Cup 2011 |
E24715
|
entity |
| Predicate | includesParticipants |
P2434
|
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: [U.S. Open Cup 2011, includesParticipants, professional clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesParticipants Context triple: [U.S. Open Cup 2011, includesParticipants, professional clubs]
-
A.
hasParticipants
chosen
Indicates that an event, activity, or situation involves one or more entities as participants in it.
-
B.
welcomesParticipantsOf
Indicates that one entity receives or greets the participants associated with another entity in a friendly or accepting manner.
-
C.
determinesParticipantIn
Indicates that one entity has the authority or role to decide or specify which other entity (or entities) will participate in a given event, activity, or process.
-
D.
participantType
Indicates the specific role or category that a participant has within a given event, activity, or relationship.
-
E.
includesPeopleOf
Indicates that a group, organization, or entity contains or encompasses certain people as its members or participants.
- 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_69a4940712c88190aa244f3fc6070a65 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4749ac8190b0fbddac2e9b2586 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.