Triple
T30680326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Negotiable Order of Withdrawal account |
E781033
|
entity |
| Predicate | mayCharge |
P96049
|
FINISHED |
| Object | monthly maintenance fees |
—
|
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: monthly maintenance fees | Statement: [Negotiable Order of Withdrawal account, mayCharge, monthly maintenance fees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayCharge Context triple: [Negotiable Order of Withdrawal account, mayCharge, monthly maintenance fees]
-
A.
canCharge
chosen
Indicates that one entity has the ability or permission to charge another entity, typically in the sense of applying a cost, fee, or electrical charge.
-
B.
hasCharge
Indicates that an entity possesses a specific electrical or formal charge, such as positive, negative, or neutral.
-
C.
mayAlsoCredit
Indicates that an additional party can optionally be acknowledged or given credit in relation to the same work, contribution, or transaction.
-
D.
containsCharge
Indicates that one entity includes, holds, or encompasses a specific charge associated with it.
-
E.
mainCharge
Indicates that one charge in a set of legal accusations is designated as the primary or most significant offense.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68b1b21308190a63dc200654683fc |
completed | May 2, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f6861170d08190bb98be609d436f84 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:32 p.m.