Triple
T11897550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LOA |
E283072
|
entity |
| Predicate | paymentTermsMayInclude |
P82462
|
FINISHED |
| Object | cash with acceptance |
—
|
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 with acceptance | Statement: [LOA, paymentTermsMayInclude, cash with acceptance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paymentTermsMayInclude Context triple: [LOA, paymentTermsMayInclude, cash with acceptance]
-
A.
conditionForPayment
Indicates the specific requirement or situation that must be satisfied before a payment is made.
-
B.
creditTermFocus
Indicates that the relationship or context specifically emphasizes or centers on the terms or conditions of credit.
-
C.
requiresPaymentOf
Indicates that one entity obligates another entity to provide a specified payment as a condition or requirement.
-
D.
paymentStructure
Indicates how payments are organized, scheduled, and divided between the involved parties.
-
E.
requiresPaymentIn
chosen
Indicates that one entity must be paid in a specified currency or payment medium in order for a related action, service, or obligation to be fulfilled.
- 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_69d6ab2a90b08190a4e818821cc93e6d |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8dd13cc10819089d8d5103e562924 |
completed | April 10, 2026, 11:20 a.m. |
| PD | Predicate disambiguation | batch_69d8bb2fca4481909893f3428b0871ac |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.