Triple
T37872838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Golden Lotus |
E944646
|
entity |
| Predicate | hasCurrencyRequirement |
P10274
|
FINISHED |
| Object | gold |
—
|
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: gold | Statement: [The Golden Lotus, hasCurrencyRequirement, gold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCurrencyRequirement Context triple: [The Golden Lotus, hasCurrencyRequirement, gold]
-
A.
hasMaximumWithdrawalRequirement
Indicates that there is an upper limit on the amount that can be withdrawn, specifying the maximum withdrawal requirement applicable to an entity or account.
-
B.
feeRequirement
Indicates that a payment or fee must be provided or satisfied as a condition for a particular action, service, or relationship to occur or remain valid.
-
C.
hasMonetaryComponent
Indicates that something includes, involves, or is associated with a monetary or financial element.
-
D.
spendingRequires
Indicates that performing a spending action is contingent upon satisfying a specified requirement or condition.
-
E.
usesSupplementaryCurrency
chosen
Indicates that an entity employs an additional, non-primary currency alongside its main currency for transactions or value exchange.
- 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_69f76eef55d481908ca6660b4b532550 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe8f74748c8190bd14a856c057f9f7 |
completed | May 9, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69fe8e7ed8088190929e0df67aca4de9 |
completed | May 9, 2026, 1:31 a.m. |
Created at: May 3, 2026, 4:19 p.m.