Triple
T1064956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Louisiana Purchase |
E22988
|
entity |
| Predicate | paymentForm |
P5428
|
FINISHED |
| Object | cash and assumption of French debts |
—
|
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: cash and assumption of French debts | Statement: [Louisiana Purchase, paymentForm, cash and assumption of French debts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paymentForm Context triple: [Louisiana Purchase, paymentForm, cash and assumption of French debts]
-
A.
paymentMethod
chosen
Indicates the means or instrument through which a payment is made in a transaction.
-
B.
paymentSystem
Indicates a relationship where one entity functions as a mechanism or platform through which another entity makes or processes payments.
-
C.
paymentDomain
Indicates the domain, context, or scope within which a payment is applicable, processed, or governed.
-
D.
paymentEnvironment
Indicates the context or setting in which a payment is initiated, processed, or completed (such as online, in-store, or in-app).
-
E.
pays
Indicates that one entity gives money or another form of compensation to another entity, typically in exchange for goods, services, or to settle a debt.
- 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b90f91248190ace1534a51b82bdd |
completed | March 1, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69a4b7359eb881909c868a558861cc18 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.