Triple
T29215388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KNEBV |
E740653
|
entity |
| Predicate | issuerLEIOfUnderlying |
P24933
|
FINISHED |
| Object | 549300T9X9Y6JV2PIA68 |
—
|
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: 549300T9X9Y6JV2PIA68 | Statement: [KNEBV, issuerLEIOfUnderlying, 549300T9X9Y6JV2PIA68]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerLEIOfUnderlying Context triple: [KNEBV, issuerLEIOfUnderlying, 549300T9X9Y6JV2PIA68]
-
A.
issuerLEI
Indicates that the subject entity is the legal entity identified as the issuer of a financial instrument, as specified by its Legal Entity Identifier (LEI).
-
B.
hasUnderlyingLEI
chosen
Indicates that an entity is associated with, or identified by, a specific underlying Legal Entity Identifier (LEI).
-
C.
industryOfUnderlyingIssuer
Indicates the industry sector to which the underlying issuer in a financial or contractual arrangement belongs.
-
D.
issuerOrganization
Indicates the organization that formally issues, grants, or authorizes a document, credential, or item.
-
E.
hasUnderlyingIssuer
Indicates that one entity serves as the fundamental or primary issuer behind another entity, such as a financial instrument or structured product.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 28, 2026, 12:13 p.m.