Triple
T35471904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cayde’s Stash |
E1025227
|
entity |
| Predicate | hasAssociatedNPC |
P170697
|
FINISHED |
| Object | Cayde-6 |
—
|
NE NERFINISHED |
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: Cayde-6 | Statement: [Cayde’s Stash, hasAssociatedNPC, Cayde-6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAssociatedNPC Context triple: [Cayde’s Stash, hasAssociatedNPC, Cayde-6]
-
A.
hasNPC
chosen
Indicates that an entity includes, is associated with, or contains a non-player character (NPC) within its context or structure.
-
B.
relationshipToNPC
Indicates the type of interpersonal or narrative connection that one entity has with a non-player character (NPC).
-
C.
representsInNPC
Indicates that one entity serves as a non-player character (NPC) representation or avatar of another entity within a system or context.
-
D.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
E.
hasProtagonistRelationship
Indicates that there exists a central, story-driving relationship involving the protagonist and another entity within a narrative.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd2839880c819099a7a89783f2270e |
completed | May 8, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69fd23dc5da48190ae8ba08947d34956 |
completed | May 7, 2026, 11:44 p.m. |
Created at: May 3, 2026, 4:04 p.m.