Triple
T107474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | establishment of the First Bank of the United States |
E2170
|
entity |
| Predicate | charterExpirationYear |
P214
|
FINISHED |
| Object | 1811 |
—
|
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: 1811 | Statement: [establishment of the First Bank of the United States, charterExpirationYear, 1811]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: charterExpirationYear Context triple: [establishment of the First Bank of the United States, charterExpirationYear, 1811]
-
A.
certificationDate
Indicates the date on which an entity was officially certified or granted a formal certification.
-
B.
endYear
chosen
Indicates the year in which an event, state, or relationship comes to an end.
-
C.
charteredIn
Indicates that an organization or entity has been formally established, authorized, or incorporated within a specified jurisdiction or location.
-
D.
isCharterMemberOf
Indicates that an entity is an original or founding member of a group, organization, or institution at the time it was established.
-
E.
hasRoyalCharter
Indicates that an entity has been formally granted a royal charter by a monarch or royal authority.
- 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a25a1199ac8190ac65ffaaf45b4f5b |
completed | Feb. 28, 2026, 2:59 a.m. |
| PD | Predicate disambiguation | batch_69a2563e7188819091e9a94e071991d7 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.