Triple
T4266308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KHL Junior Draft |
E96831
|
entity |
| Predicate | prospectStatus |
P55074
|
FINISHED |
| Object | players not yet established in KHL |
—
|
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: players not yet established in KHL | Statement: [KHL Junior Draft, prospectStatus, players not yet established in KHL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prospectStatus Context triple: [KHL Junior Draft, prospectStatus, players not yet established in KHL]
-
A.
profitStatus
Indicates the financial performance state of an entity, such as whether it is operating at a profit, loss, or breaking even.
-
B.
seeksStatusAs
Indicates that one entity is attempting to obtain or be recognized with a particular status, role, or standing in relation to another entity.
-
C.
applicantState
Indicates the current status or condition assigned to an applicant within a process or system.
-
D.
applicantStates
Indicates that an applicant explicitly declares or asserts a particular fact, condition, or piece of information.
-
E.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
- F. None of above. chosen
Provenance (4 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_69b34543f06c8190915ebb1a4574ffa9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34fcc383c81908e17da7cbc86a630 |
completed | March 12, 2026, 11:44 p.m. |
| PD | Predicate disambiguation | batch_69b347f8dcb08190a725c1f7fb5a7466 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e0606488190baadf469a1afc3c2 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:07 p.m.