Triple
T37515431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Betrayal |
E932621
|
entity |
| Predicate | addsItemType |
P161404
|
FINISHED |
| Object | Veiled item |
—
|
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: Veiled item | Statement: [Betrayal, addsItemType, Veiled item]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsItemType Context triple: [Betrayal, addsItemType, Veiled item]
-
A.
addsNPCType
Indicates that one entity introduces or registers a specific type of non-player character (NPC) into a system, context, or environment.
-
B.
canBeAddedTo
Indicates that one entity is capable of being combined or incorporated with another entity, typically without conflict or incompatibility.
-
C.
addsNewGear
Indicates that an entity introduces or incorporates additional gear into an existing set, system, or configuration.
-
D.
addsObjectType
chosen
Indicates that an entity introduces or includes a specific type of object into a collection, structure, or context.
-
E.
addsCardType
Indicates that one entity introduces or associates a specific card type with another entity or collection.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fba5eec0448190a5e6f0c43fdcd0e3 |
completed | May 6, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69fba34edd548190bfa980e6e16e0a88 |
completed | May 6, 2026, 8:23 p.m. |
Created at: May 3, 2026, 4:17 p.m.