Triple
T27656609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Municipal Credit Union |
E697010
|
entity |
| Predicate | financialProduct |
P163320
|
FINISHED |
| Object | loan products |
—
|
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: loan products | Statement: [Municipal Credit Union, financialProduct, loan products]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: financialProduct Context triple: [Municipal Credit Union, financialProduct, loan products]
-
A.
financialProduct
chosen
Indicates that there is a relationship in which one entity is a financial instrument or service offered to, held by, or associated with another entity.
-
B.
financialProductCategory
Indicates the classification or type of a financial product within a defined category system.
-
C.
alsoProvidesFinanceIn
Indicates that an entity, in addition to other roles or services, supplies financial support or funding within a specified context or location.
-
D.
investmentType
Indicates the specific category or nature of an investment associated with an entity or transaction.
-
E.
financeScope
Indicates the financial coverage, limits, or extent to which a particular action, agreement, or responsibility applies.
- 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_69ef590abd3c8190834d0193bde12007 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 2:34 p.m.