Triple
T29357111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kyle Bradway |
E744474
|
entity |
| Predicate | hasSkillLevel |
P148255
|
FINISHED |
| Object | limited acting talent |
—
|
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: limited acting talent | Statement: [Kyle Bradway, hasSkillLevel, limited acting talent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSkillLevel Context triple: [Kyle Bradway, hasSkillLevel, limited acting talent]
-
A.
requiresSkillLevel
Indicates that performing or engaging in something depends on possessing at least a specified level of skill.
-
B.
includeSkillLevel
chosen
Indicates that a specified skill is associated with an entity together with a particular proficiency or mastery level.
-
C.
hasSkillTree
Indicates that an entity is associated with a structured progression of skills or abilities, typically organized in a branching or hierarchical form.
-
D.
servesSkillLevel
Indicates that one entity provides or is appropriate for a particular level of skill in another entity.
-
E.
requiresSkill
Indicates that performing or engaging in one entity (e.g., a task or role) depends on possessing or applying a specific skill represented by the other entity.
- 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66984ecf48190bd8ccfcfee1c55af |
completed | May 2, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:13 p.m.