Triple
T360054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Bank of the United States |
E7829
|
entity |
| Predicate | publicOwnershipShare |
P12336
|
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: [First Bank of the United States, publicOwnershipShare, 20 percent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicOwnershipShare Context triple: [First Bank of the United States, publicOwnershipShare, 20 percent]
-
A.
sharesOwnershipWith
Indicates that two or more entities jointly hold ownership rights or stakes in the same asset, resource, or organization.
-
B.
privateShareOfStock
Indicates that one entity privately transfers or allocates shares of stock to another entity, outside of a public market transaction.
-
C.
homeGroundSharedWith
Indicates that two teams or organizations use the same venue or location as their home ground.
-
D.
isSharedBy
Indicates that something is jointly possessed, used, or experienced by two or more entities.
-
E.
sharesPowerWith
Indicates that two or more entities jointly hold, exercise, or distribute authority or control in a shared manner.
- F. None of above. chosen
Provenance (4 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebccb8d88190a31f7c443a0c8566 |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95aeed48190b5e48865cc964938 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea2c44408190946267525c88e811 |
completed | Feb. 28, 2026, 1:14 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.