Triple
T38313540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gunantuna |
E1033760
|
entity |
| Predicate | shellMoneyUse |
P160814
|
FINISHED |
| Object | bridewealth payments |
—
|
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: bridewealth payments | Statement: [Gunantuna, shellMoneyUse, bridewealth payments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shellMoneyUse Context triple: [Gunantuna, shellMoneyUse, bridewealth payments]
-
A.
usesShellMoneyFor
chosen
Indicates that an entity employs shell money as a medium of payment or exchange for another entity or purpose.
-
B.
usedFund
Indicates that one entity expended or applied a particular fund or financial resource for some purpose.
-
C.
incomeUsedFor
Indicates that some or all of an income amount is allocated or spent for a specified purpose, activity, or recipient.
-
D.
usesCurrency
Indicates that one entity conducts its financial transactions or values using the monetary unit represented by the other entity.
-
E.
spendingRequires
Indicates that performing a spending action is contingent upon satisfying a specified requirement or condition.
- 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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcd1499e2c81909bafd84dc4810f45 |
completed | May 7, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69fcccf024ec819086383ffbb6cfc036 |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 3, 2026, 4:30 p.m.