Triple
T496005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Bank of the United States |
E10294
|
entity |
| Predicate | finalFailure |
P4339
|
FINISHED |
| Object | 1841 |
—
|
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: 1841 | Statement: [Second Bank of the United States, finalFailure, 1841]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalFailure Context triple: [Second Bank of the United States, finalFailure, 1841]
-
A.
missionFailure
Indicates that an attempted mission or operation did not achieve its intended objectives or outcome.
-
B.
finalStep
Indicates that an action or state represents the last step or concluding stage in a process or sequence.
-
C.
finalDisposition
chosen
Indicates the ultimate outcome, status, or resolution assigned to an entity after all relevant processes or decisions are complete.
-
D.
failsWhen
Indicates that a particular action, process, or condition does not succeed under the specified circumstances or triggers.
-
E.
fault
Indicates that one entity is responsible or at blame for a problem, error, or undesirable outcome involving another entity or 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f115334881908ac5ab96c7f4214e |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edf90ca88190b6a182e5b6733612 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.