Triple
T37513774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Travincal |
E932578
|
entity |
| Predicate | containsNPC |
P170697
|
FINISHED |
| Object | Zakarum High Council members |
E2230096
|
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: Zakarum High Council members | Statement: [Travincal, containsNPC, Zakarum High Council members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsNPC Context triple: [Travincal, containsNPC, Zakarum High Council members]
-
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.
representsInNPC
Indicates that one entity serves as a non-player character (NPC) representation or avatar of another entity within a system or context.
-
D.
hasCreature
Indicates that one entity possesses, contains, or is associated with a particular creature.
-
E.
supportsNPCs
Indicates that an entity provides functionality or compatibility for non-player characters (NPCs) within a system or environment.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a01b3af7b908190b4675c85d32d106c |
completed | May 11, 2026, 10:47 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40afd23c9881908eb880a584bb3414 |
completed | June 28, 2026, 5:23 a.m. |
| PD | Predicate disambiguation | batch_6a01b35813c081908e484b2b9ca5dd05 |
completed | May 11, 2026, 10:45 a.m. |
Created at: May 3, 2026, 4:17 p.m.