Triple
T13273509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US0846707026 |
E316127
|
entity |
| Predicate | ISINCode |
P5717
|
FINISHED |
| Object | US0846707026 |
—
|
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: US0846707026 | Statement: [US0846707026, ISINCode, US0846707026]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ISINCode Context triple: [US0846707026, ISINCode, US0846707026]
-
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.
associatedCompanyISINCountryCode
Indicates that the relationship links a company to the country code corresponding to the ISIN of an associated company.
-
E.
parentCompanyISIN
Indicates that the subject entity is associated with a parent company identified by the given ISIN (International Securities Identification Number).
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:26 p.m.