Triple
T18702749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAN |
E457291
|
entity |
| Predicate | issuerSubsector |
P100187
|
FINISHED |
| Object | diversified banks |
—
|
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: diversified banks | Statement: [SAN, issuerSubsector, diversified banks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: issuerSubsector Context triple: [SAN, issuerSubsector, diversified banks]
-
A.
ownerSector
Indicates the sector or industry category to which the owner of an entity belongs.
-
B.
industryOfUnderlyingIssuer
chosen
Indicates the industry sector to which the underlying issuer in a financial or contractual arrangement belongs.
-
C.
isSectorSpecific
Indicates that something is tailored or restricted to a particular industry or sector rather than being generally applicable.
-
D.
issuerType
Indicates the classification or category of the entity that issues something (such as a document, credential, or instrument).
-
E.
issuerSpecialization
Indicates the particular field, domain, or area of expertise in which the issuer is specialized.
- 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_69d8d392aad081909fe31aa03e6e97d1 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e56714d0588190ac050356bc2784fd |
completed | April 19, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69e478de85088190ba5f005f1d39f587 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:49 a.m.