Triple
T32392187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RUA:IND |
E827700
|
entity |
| Predicate | hasBloombergTickerType |
P5721
|
FINISHED |
| Object | IND |
—
|
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: IND | Statement: [RUA:IND, hasBloombergTickerType, IND]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBloombergTickerType Context triple: [RUA:IND, hasBloombergTickerType, IND]
-
A.
hasBloombergTickerFormat
Indicates that an entity’s identifier follows the standardized ticker symbol format used by Bloomberg.
-
B.
hasTickerType
chosen
Indicates that an entity is associated with a specific type or category of ticker (e.g., stock, index, or other financial instrument ticker).
-
C.
hasTickerCountryCode
Indicates that a financial instrument’s ticker symbol is associated with a specific country code.
-
D.
isMajorBankTicker
Indicates that a given ticker symbol corresponds to a major, systemically important banking institution.
-
E.
hasCorporateTickerRoot
Indicates that a company’s stock ticker symbol is derived from or based on the specified root string.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c20f209081909fb9ac8f95069f04 |
completed | May 3, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:52 a.m.