Triple
T29655147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dark Archon |
E750243
|
entity |
| Predicate | canUseAbility |
P45916
|
FINISHED |
| Object | Mind Control |
—
|
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: Mind Control | Statement: [Dark Archon, canUseAbility, Mind Control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canUseAbility Context triple: [Dark Archon, canUseAbility, Mind Control]
-
A.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
B.
hasProtagonistAbility
Indicates that a protagonist possesses a specific ability, power, or special skill.
-
C.
canBeUsed
Indicates that one entity is suitable or available to serve a particular function, purpose, or role in relation to another entity or context.
-
D.
hasAbilityEffect
Indicates that one entity possesses or produces a specific ability-related effect on another entity or context.
-
E.
canPerform
chosen
Indicates that one entity has the ability, permission, or capacity to carry out a specific action or function on or with another 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f676f968d08190a4adba0439b438c9 |
completed | May 2, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 28, 2026, 6:54 p.m.