Triple
T36954290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reaper’s Bones |
E914148
|
entity |
| Predicate | lootPreference |
P186790
|
FINISHED |
| Object | stolen emissary loot |
—
|
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: stolen emissary loot | Statement: [Reaper’s Bones, lootPreference, stolen emissary loot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lootPreference Context triple: [Reaper’s Bones, lootPreference, stolen emissary loot]
-
A.
LootType
Indicates the type or category of loot associated with an entity or event.
-
B.
armorPreference
Indicates a character’s favored type or style of armor they typically choose to wear or use.
-
C.
weaponPreference
Indicates a relationship where an entity favors or typically uses a particular type of weapon over others.
-
D.
lootTableIncludes
Indicates that a particular loot table contains or can yield a specified item or reward.
-
E.
plunderedItem
Indicates that an item has been taken or looted by force, typically during a raid, conflict, or act of theft.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fa0a799b9081909bfa8293a22c4b00 |
completed | May 5, 2026, 3:19 p.m. |
Created at: May 3, 2026, 4:13 p.m.