Triple
T38593488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angelic Descent |
E932506
|
entity |
| Predicate | skillCeiling |
P191270
|
FINISHED |
| Object | high when combined with Guardian Angel tech |
—
|
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: high when combined with Guardian Angel tech | Statement: [Angelic Descent, skillCeiling, high when combined with Guardian Angel tech]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skillCeiling Context triple: [Angelic Descent, skillCeiling, high when combined with Guardian Angel tech]
-
A.
skillFactor
Indicates the degree or level of skill associated with an entity in performing a particular task or activity.
-
B.
skillType
Indicates the specific category or kind of skill that characterizes or classifies an associated skill-related entity or action.
-
C.
requiresSkillLevel
Indicates that performing or engaging in something depends on possessing at least a specified level of skill.
-
D.
killsAt
Indicates that one entity causes the death of another entity at a specific time or event.
-
E.
servesSkillLevel
Indicates that one entity provides or is appropriate for a particular level of skill in another entity.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdb0de8c08190928cd1323f80ab5c |
completed | May 7, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69fcd9017dd88190b32a73fe78909740 |
completed | May 7, 2026, 6:25 p.m. |
| PDg | Predicate description generation | batch_69fcdb0cf6008190b27046b694f84356 |
completed | May 7, 2026, 6:33 p.m. |
Created at: May 3, 2026, 4:32 p.m.