Triple
T18226806
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloomberg Government |
E436441
|
entity |
| Predicate | hasDeliveryChannel |
P130074
|
FINISHED |
| Object | online portal |
—
|
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: online portal | Statement: [Bloomberg Government, hasDeliveryChannel, online portal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeliveryChannel Context triple: [Bloomberg Government, hasDeliveryChannel, online portal]
-
A.
isDeliveredThrough
chosen
Indicates that something is transmitted, conveyed, or provided by means of a specified channel, method, or medium.
-
B.
hasMarketingChannel
Indicates that an entity utilizes or is associated with a particular marketing channel for promotion or communication.
-
C.
hasShippingLaneType
Indicates the specific category or type of shipping lane associated with a given route or area.
-
D.
offersDelivery
Indicates that a provider makes goods or services available to be transported and delivered to a recipient’s specified location.
-
E.
offersDeliveryTo
Indicates that one entity provides delivery services to another entity or location.
- 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_69d8b9103a8081908bbb0836fef10efd |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f4aff8748190be5e732f9dbc8dff |
completed | April 19, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69e4332336cc8190808b9c70c888ba65 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.