Triple
T22449895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UA |
E554962
|
entity |
| Predicate | associatedWithCompanyISIN |
P51457
|
FINISHED |
| Object | US9043111072 |
—
|
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: US9043111072 | Statement: [UA, associatedWithCompanyISIN, US9043111072]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithCompanyISIN Context triple: [UA, associatedWithCompanyISIN, US9043111072]
-
A.
associatedCompanyISINCountryCode
Indicates that the relationship links a company to the country code corresponding to the ISIN of an associated company.
-
B.
parentCompanyISIN
Indicates that the subject entity is associated with a parent company identified by the given ISIN (International Securities Identification Number).
-
C.
associatedWithTicker
Indicates that an entity is linked or connected to a specific stock market ticker symbol.
-
D.
hasAssociatedCompany
chosen
Indicates that one entity is linked or connected to a company in an associated or affiliated manner.
-
E.
relatedCompanyType
Indicates the type or nature of the relationship that one company has to another company.
- 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_69e11e5113208190ab58c6b595f9d1d0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b4ae8a08190ba6027f036ce62af |
completed | April 29, 2026, 1:13 a.m. |
| PD | Predicate disambiguation | batch_69e898ad961c819098fd1e46129bddcc |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.