Triple
T37873983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Silver Enclave |
E944671
|
entity |
| Predicate | hasNotableNPC |
P170697
|
FINISHED |
| Object | Rhonin |
E2234796
|
NE 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: Rhonin | Statement: [Silver Enclave, hasNotableNPC, Rhonin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableNPC Context triple: [Silver Enclave, hasNotableNPC, Rhonin]
-
A.
hasNPC
chosen
Indicates that an entity includes, is associated with, or contains a non-player character (NPC) within its context or structure.
-
B.
hasNotableHero
Indicates that an entity is associated with a particularly distinguished or prominent hero.
-
C.
hasNotableCharacterDynamic
Indicates that there is a particularly distinctive, memorable, or significant pattern of interaction or relationship between the involved characters.
-
D.
hasNotableTribeAtEncounter
Indicates that, at the time of the encounter, the entity was associated with or identified as belonging to a notable tribe.
-
E.
hasNotableResident
Indicates that an entity is or has been a well-known or distinguished resident of a particular place or location.
- F. None of above.
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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a412c9d4d0481908c0477c51b544d72 |
completed | June 28, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:19 p.m.