Triple
T495981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Bank of the United States |
E10294
|
entity |
| Predicate | governmentOwnershipShare |
P7882
|
FINISHED |
| Object | 20 percent |
—
|
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: 20 percent | Statement: [Second Bank of the United States, governmentOwnershipShare, 20 percent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentOwnershipShare Context triple: [Second Bank of the United States, governmentOwnershipShare, 20 percent]
-
A.
ownershipStructure
Indicates how ownership or control is distributed among entities within an organization or asset.
-
B.
sharesOwnershipStructureWith
Indicates that two entities have the same or closely aligned ownership structure, such as sharing the same owners, parent company, or control hierarchy.
-
C.
federalShareOfStock
chosen
Indicates the proportion or amount of stock in an entity that is owned or held by the federal government.
-
D.
ownershipType
Indicates the specific nature or category of the ownership relationship that one entity holds over another.
-
E.
ownedBy
Indicates that one entity possesses legal or rightful ownership of another entity.
- 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.