Triple
T1001388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BA |
E21609
|
entity |
| Predicate | issuerCUSIP |
P22170
|
FINISHED |
| Object | 097023105 |
—
|
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: 097023105 | Statement: [BA, issuerCUSIP, 097023105]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerCUSIP Context triple: [BA, issuerCUSIP, 097023105]
-
A.
hasCUSIP
Indicates that a financial instrument is associated with a specific CUSIP identifier assigned to it.
-
B.
hasCIK
Indicates that an entity is associated with a specific Central Index Key (CIK) identifier, typically used for uniquely identifying it in regulatory or financial filings.
-
C.
issuerType
Indicates the classification or category of the entity that issues something (such as a document, credential, or instrument).
-
D.
ISIN
Indicates that an entity is identified or associated with a specific International Securities Identification Number (ISIN).
-
E.
issuedBy
Indicates that something (such as a document, order, or statement) has been formally created, authorized, or released by a particular agent or authority.
- 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_69a493c53e648190ae8cb76c433fd9a7 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b4fcbc04819098d2125518f62ae7 |
completed | March 1, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69a4b2b1f4f88190822598cfd2a0fd2b |
completed | March 1, 2026, 9:42 p.m. |
| PDg | Predicate description generation | batch_69a4b36064a48190b85c402f32cbadd1 |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:41 p.m.