Triple
T24219929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stalnye Lisy |
E601418
|
entity |
| Predicate | affiliatedClubPlaysInLeague |
P41657
|
FINISHED |
| Object | KHL |
—
|
NE NERFINISHED |
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: KHL | Statement: [Stalnye Lisy, affiliatedClubPlaysInLeague, KHL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affiliatedClubPlaysInLeague Context triple: [Stalnye Lisy, affiliatedClubPlaysInLeague, KHL]
-
A.
associatedClub2
Indicates that an entity has a secondary or additional affiliation or membership with a particular club.
-
B.
associatedClub1
Indicates that an entity has a primary or first-listed association with a particular club or organization.
-
C.
associatedClubSport
Indicates that there is a relationship between a club and the sport with which it is connected or aligned.
-
D.
basedInLeague
chosen
Indicates that an entity (such as a team or club) participates in, belongs to, or is officially associated with a particular league.
-
E.
affiliateLeague
Indicates that one sports organization or team is formally associated with and operates under the umbrella or partnership of a particular league.
- 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_69e29537ca548190b94a37ebe1977caf |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f2820cdd3c8190998d6d901224c09f |
completed | April 29, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:59 p.m.