Triple
T32392173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RUA:IND |
E827700
|
entity |
| Predicate | hasDataProvider |
P141050
|
FINISHED |
| Object | Bloomberg |
—
|
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: Bloomberg | Statement: [RUA:IND, hasDataProvider, Bloomberg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDataProvider Context triple: [RUA:IND, hasDataProvider, Bloomberg]
-
A.
usedByDataProvider
Indicates that something (such as a resource, tool, or method) is utilized or consumed by a data provider in the course of supplying or managing data.
-
B.
hasDataFields
Indicates that an entity possesses or is associated with specific data fields or attributes.
-
C.
hasIndexProvider
Indicates that an entity is associated with or uses a specific index provider responsible for supplying indexing capabilities or services.
-
D.
hasDataDomain
Indicates that something is associated with, constrained by, or operates within a particular data domain or scope of data.
-
E.
hasSourceOfData
chosen
Indicates that one entity serves as the origin or provider of the data used or referenced by another entity.
- 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_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 12:52 a.m.