Triple
T37470673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kleia |
E931143
|
entity |
| Predicate | canSoulbindWith |
P188374
|
FINISHED |
| Object | player characters |
—
|
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: player characters | Statement: [Kleia, canSoulbindWith, player characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canSoulbindWith Context triple: [Kleia, canSoulbindWith, player characters]
-
A.
isSoulbindFor
Indicates that one entity is magically or spiritually bound to another in a way that links their fates or abilities.
-
B.
includesExampleSoulbindNPC
Indicates that something contains or features a specific example of a soulbound non-player character (NPC) as part of its content or configuration.
-
C.
hasSoulGemAbility
Indicates that an entity possesses the capability to use, interact with, or be affected by a soul gem and its associated powers or functions.
-
D.
associatedWithSoulsOf
Indicates a relationship in which something is connected, linked, or related specifically to the souls of certain entities.
-
E.
canBeEnchantedWith
Indicates that an entity is capable of receiving or being affected by a specified enchantment.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba68077788190b311e027435fcf87 |
completed | May 6, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69fba34c65ac8190b298f0f00d1dcc0e |
completed | May 6, 2026, 8:23 p.m. |
| PDg | Predicate description generation | batch_69fba67f78348190ab160988e4698394 |
completed | May 6, 2026, 8:37 p.m. |
Created at: May 3, 2026, 4:17 p.m.