Triple
T30680307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Negotiable Order of Withdrawal account |
E781033
|
entity |
| Predicate | typicallyOfferedTo |
P134635
|
FINISHED |
| Object | consumers |
—
|
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: consumers | Statement: [Negotiable Order of Withdrawal account, typicallyOfferedTo, consumers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicallyOfferedTo Context triple: [Negotiable Order of Withdrawal account, typicallyOfferedTo, consumers]
-
A.
offeredIn
Indicates that something is made available or provided within a particular context, setting, or medium.
-
B.
providesOfferingsTo
Indicates that one entity supplies or presents offerings, such as goods, services, or benefits, to another entity.
-
C.
offeredOver
Indicates that one entity has been proposed, presented, or made available to another entity as an option or opportunity.
-
D.
mayBeOfferedFor
chosen
Indicates that one entity can potentially be provided or made available as an option to another entity.
-
E.
offeringType
Indicates the category or nature of what is being offered in a transaction or interaction (e.g., product, service, or other type of offering).
- 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_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:32 p.m.