Triple
T2375156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Credit Union Administration |
E46180
|
entity |
| Predicate | insures |
P18388
|
FINISHED |
| Object | credit union deposits |
—
|
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: credit union deposits | Statement: [National Credit Union Administration, insures, credit union deposits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: insures Context triple: [National Credit Union Administration, insures, credit union deposits]
-
A.
insurance
chosen
Indicates a relationship where one party provides financial protection or coverage to another against specified risks or losses, typically in exchange for payment.
-
B.
ensures
Indicates that one entity guarantees or makes certain that a particular condition, outcome, or state holds for another entity or situation.
-
C.
protects
Indicates taking action to keep someone or something safe from harm, danger, or negative effects.
-
D.
insuranceType
Indicates the specific category or kind of insurance coverage associated with an entity or relationship.
-
E.
guaranteeCoverage
Indicates that one party commits to providing financial or protective coverage for another party or specified situation.
- 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_69a88a145268819083e2736cb835c696 |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abca4d89248190be7d712d5fa8382b |
completed | March 7, 2026, 6:48 a.m. |
| PD | Predicate disambiguation | batch_69abc59d82f08190b7c36982d1ae783d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:56 p.m.