Triple
T38584664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Steamvault |
E932318
|
entity |
| Predicate | hasNagaForces |
P201386
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Steamvault, hasNagaForces, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNagaForces Context triple: [The Steamvault, hasNagaForces, true]
-
A.
hasNandi
Indicates that an entity possesses, is associated with, or is accompanied by a Nandi (typically a bull or Nandi-related object/feature).
-
B.
hasNPC
Indicates that an entity includes, is associated with, or contains a non-player character (NPC) within its context or structure.
-
C.
hasShamans
Indicates that an entity possesses, employs, or is associated with one or more shamans.
-
D.
hasTamga
Indicates that an entity bears or is marked with a specific tamga (a distinctive emblem, brand, or clan/ownership mark).
-
E.
hasForceCarrier
Indicates that a fundamental interaction or force is mediated or carried by a specific particle or field.
- F. None of above. chosen
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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ffef812da48190b875a7376b24f92d |
completed | May 10, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69ffedecd580819097851b1473fdd6ed |
completed | May 10, 2026, 2:31 a.m. |
| PDg | Predicate description generation | batch_69ffef8003c081909ec2413b4ea08d43 |
completed | May 10, 2026, 2:37 a.m. |
Created at: May 3, 2026, 4:32 p.m.