Triple
T32807870
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DE000BASF111 |
E839064
|
entity |
| Predicate | hasISINStandard |
P139503
|
FINISHED |
| Object | ISO 6166 |
—
|
NE NERFINISHED |
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: ISO 6166 | Statement: [DE000BASF111, hasISINStandard, ISO 6166]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasISINStandard Context triple: [DE000BASF111, hasISINStandard, ISO 6166]
-
A.
hasISIN
Indicates that a financial instrument is associated with a specific International Securities Identification Number (ISIN) that uniquely identifies it.
-
B.
ISINFormat
chosen
Indicates that a given string conforms to the standardized International Securities Identification Number (ISIN) format.
-
C.
ISIN
Indicates that an entity is identified or associated with a specific International Securities Identification Number (ISIN).
-
D.
hadISINCountryCode
Indicates that an entity was associated with a financial instrument whose ISIN code used a specific country code at some point in time.
-
E.
ISINCountry
Indicates that an entity is located within, belongs to, or is situated inside a specified country.
- 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc5740fc81909774a4f65201a3ff |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:15 a.m.