Triple
T17476607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AHL All-Star Classic |
E425553
|
entity |
| Predicate | skillsFormat |
P127601
|
FINISHED |
| Object | individual skills contests |
—
|
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: individual skills contests | Statement: [AHL All-Star Classic, skillsFormat, individual skills contests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skillsFormat Context triple: [AHL All-Star Classic, skillsFormat, individual skills contests]
-
A.
skillSet
Indicates that an entity possesses or is associated with a particular collection of skills or competencies.
-
B.
skilledIn
Indicates that an entity possesses ability, expertise, or proficiency in performing or using another entity (such as a task, tool, or domain).
-
C.
killsAsPartOfJob
Indicates that one entity kills another as a regular or expected duty within their professional role or occupation.
-
D.
skillEmphasis
Indicates that a particular skill is given special focus, priority, or importance within a context such as a role, task, or curriculum.
-
E.
notableRecruitingSkill
Indicates that an entity is recognized for having significant or distinguished ability in recruiting others.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451bc3f908190b2c7a2d1f75a43f2 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:47 a.m.