Triple
T37470800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dreamweaver |
E931146
|
entity |
| Predicate | soulbindFor |
P187797
|
FINISHED |
| Object | Night Fae players |
—
|
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: Night Fae players | Statement: [Dreamweaver, soulbindFor, Night Fae players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soulbindFor Context triple: [Dreamweaver, soulbindFor, Night Fae players]
-
A.
soulbindSystem
Indicates a game mechanic where a character permanently links an item, ability, or entity to themselves so it cannot be transferred or used by others.
-
B.
isSoulbindFor
chosen
Indicates that one entity is magically or spiritually bound to another in a way that links their fates or abilities.
-
C.
canSoulbindWith
Indicates that one entity is capable of forming a soulbound or spiritually bound connection with another entity.
-
D.
includesExampleSoulbindNPC
Indicates that something contains or features a specific example of a soulbound non-player character (NPC) as part of its content or configuration.
-
E.
associatedWithSoulsOf
Indicates a relationship in which something is connected, linked, or related specifically to the souls of certain entities.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.