Triple
T26924979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESL Pro League |
E677750
|
entity |
| Predicate | hasPartnerTeams |
P27502
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [ESL Pro League, hasPartnerTeams, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPartnerTeams Context triple: [ESL Pro League, hasPartnerTeams, yes]
-
A.
hasPartnerInSport
Indicates that one entity has another entity as a partner with whom they jointly participate in a sport or sporting activity.
-
B.
hasPartner
Indicates that one entity is in a partner relationship (such as romantic, life, or business partnership) with another entity.
-
C.
hasPartnerOrganization
chosen
Indicates that an entity is formally associated or collaborates with another entity as a partner organization.
-
D.
hasCompanionTeamName
Indicates that an entity is associated with a companion team identified by the given team name.
-
E.
hasTeamFor
Indicates that an entity possesses, is associated with, or is responsible for a specific team designated for a particular purpose or context.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 27, 2026, 6:09 a.m.