Triple
T424338
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECHL |
E8172
|
entity |
| Predicate | playerContractType |
P405
|
FINISHED |
| Object | professional |
—
|
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 | Statement: [ECHL, playerContractType, professional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playerContractType Context triple: [ECHL, playerContractType, professional]
-
A.
typeOfContract
chosen
Indicates the specific kind or category of contractual agreement that applies between the related entities.
-
B.
employmentType
Indicates the specific kind or category of employment relationship that exists between an individual and an employer (e.g., full-time, part-time, contract).
-
C.
salaryType
Indicates the classification or structure of compensation associated with an entity, such as whether pay is salaried, hourly, commission-based, or another type.
-
D.
personnelType
Indicates the classification or role category assigned to a person within an organization or system.
-
E.
typeOfRole
Indicates that one entity specifies the kind or category of role that another entity holds or performs.
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eed3e4cc8190ba6aff3bd1adb06f |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd5439c8190aea661b8b4aa51e9 |
completed | Feb. 28, 2026, 1:29 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.