Triple
T25535761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexa Developer Console |
E640033
|
entity |
| Predicate | supportsSkillType |
P24486
|
FINISHED |
| Object | custom skills |
—
|
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: custom skills | Statement: [Alexa Developer Console, supportsSkillType, custom skills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSkillType Context triple: [Alexa Developer Console, supportsSkillType, custom skills]
-
A.
indicatesSkill
Indicates a relationship where one entity possesses, demonstrates, or is associated with a particular skill represented by another entity.
-
B.
supportsType
chosen
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
C.
skillType
Indicates the specific category or kind of skill that characterizes or classifies an associated skill-related entity or action.
-
D.
supportsCompetency
Indicates that one entity provides the basis, evidence, or reinforcement for the development, validation, or demonstration of a particular competency.
-
E.
supportsMissionType
Indicates that one entity is capable of handling, enabling, or being compatible with a specified type of mission.
- 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_69e75dbfff7081909b0aa779d48321d2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: April 21, 2026, 3:22 p.m.