Triple
T5261494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BA:US |
E118833
|
entity |
| Predicate | hasBloombergUniqueIdType |
P1285
|
FINISHED |
| Object | ticker |
—
|
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: ticker | Statement: [BA:US, hasBloombergUniqueIdType, ticker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBloombergUniqueIdType Context triple: [BA:US, hasBloombergUniqueIdType, ticker]
-
A.
hasBusinessTypeAlong
Indicates that a business or commercial entity located along a route, corridor, or area is associated with a specific type or category of business activity.
-
B.
hasISIN
Indicates that a financial instrument is associated with a specific International Securities Identification Number (ISIN) that uniquely identifies it.
-
C.
isBroadMarketBenchmark
Indicates that something serves as a broad market benchmark, representing the overall performance of a wide, diversified segment of a market rather than a narrow or specialized subset.
-
D.
recognizedByBIE
Indicates that something has been formally acknowledged or certified by the Bureau International des Expositions (BIE).
-
E.
hasIdentifierSystem
chosen
Indicates that an entity is associated with a particular system or scheme used to assign and manage its identifiers.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bd0c5f48190a1be89314c59f96b |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.