Triple
T10502686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ABT |
E247709
|
entity |
| Predicate | associatedCompanyISIN |
P5717
|
FINISHED |
| Object | US0028241000 |
—
|
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: US0028241000 | Statement: [ABT, associatedCompanyISIN, US0028241000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedCompanyISIN Context triple: [ABT, associatedCompanyISIN, US0028241000]
-
A.
ISIN
Indicates that an entity is identified or associated with a specific International Securities Identification Number (ISIN).
-
B.
hasISIN
chosen
Indicates that a financial instrument is associated with a specific International Securities Identification Number (ISIN) that uniquely identifies it.
-
C.
ISINCountry
Indicates that an entity is located within, belongs to, or is situated inside a specified country.
-
D.
underlyingCompanyPrimaryListingTicker
Indicates the stock ticker symbol of the primary exchange listing for the underlying company.
-
E.
underlyingCompanyTicker
Indicates that one entity is the stock ticker symbol corresponding to the underlying company of another financial instrument or 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_69d381c4aa948190942e1d803143fb0e |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5099c6a848190bf1d5361e9e61108 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8e24ac8190912c9f11b8bd3084 |
completed | April 7, 2026, 12:41 p.m. |
Created at: April 6, 2026, 12:25 p.m.