Triple
T4894117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. savings banks |
E109631
|
entity |
| Predicate | typicalCharter |
P19150
|
FINISHED |
| Object | state savings bank charter |
—
|
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: state savings bank charter | Statement: [U.S. savings banks, typicalCharter, state savings bank charter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalCharter Context triple: [U.S. savings banks, typicalCharter, state savings bank charter]
-
A.
charterType
chosen
Indicates the specific category or kind of charter under which an entity, agreement, or operation is formally established or governed.
-
B.
charterFeature
Indicates that an entity (such as a service, product, or offering) includes or provides a specific feature as part of a charter or special arrangement.
-
C.
clubCharter
Indicates that there exists a formal charter or foundational document that defines the rules, purpose, and governance structure of a club.
-
D.
charterRevised
Indicates that an existing charter has been modified or updated from its previous version.
-
E.
charterName
Indicates the official name or title assigned in a charter that defines or authorizes an entity or arrangement.
- 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_69bd4410bbf88190aad50d2451c863d6 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ffabccc81909115ece1b04e2061 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c2e7b5c8190b8bf9d616dfa24f0 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:28 p.m.