Triple
T37873979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver Enclave |
E944671
|
entity |
| Predicate | containsNPCType |
P170697
|
FINISHED |
| Object | Kirin Tor magi |
—
|
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: Kirin Tor magi | Statement: [Silver Enclave, containsNPCType, Kirin Tor magi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsNPCType Context triple: [Silver Enclave, containsNPCType, Kirin Tor magi]
-
A.
hasNPC
chosen
Indicates that an entity includes, is associated with, or contains a non-player character (NPC) within its context or structure.
-
B.
requiresNPC
Indicates that one entity depends on the presence, involvement, or assistance of a non-player character (NPC) in order to occur, be valid, or be completed.
-
C.
addsNPCType
Indicates that one entity introduces or registers a specific type of non-player character (NPC) into a system, context, or environment.
-
D.
representsInNPC
Indicates that one entity serves as a non-player character (NPC) representation or avatar of another entity within a system or context.
-
E.
heldByCharacterType
Indicates that something (such as an item, role, or status) is possessed or carried by a character of a specified type.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a01ccd995e48190b6675e463bd0a567 |
completed | May 11, 2026, 12:34 p.m. |
| PD | Predicate disambiguation | batch_6a01cc33177c8190bc0703276618b3ec |
completed | May 11, 2026, 12:31 p.m. |
Created at: May 3, 2026, 4:19 p.m.