Triple
T36954178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Order of Souls |
E914146
|
entity |
| Predicate | acceptsAsPayment |
P46101
|
FINISHED |
| Object | Bounty skulls |
—
|
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: Bounty skulls | Statement: [Order of Souls, acceptsAsPayment, Bounty skulls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: acceptsAsPayment Context triple: [Order of Souls, acceptsAsPayment, Bounty skulls]
-
A.
acceptsFundingFrom
Indicates that one entity receives financial support or funding from another entity.
-
B.
canBePaidTo
Indicates that one entity is allowed or able to transfer payment to another entity.
-
C.
hasPaymentOption
chosen
Indicates that an entity supports or offers a particular method or option for making payments.
-
D.
cardAcceptance
Indicates that one party accepts or recognizes another party’s card as a valid form of payment or identification.
-
E.
requiresPaymentOf
Indicates that one entity obligates another entity to provide a specified payment as a condition or requirement.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:13 p.m.