Triple
T17922367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICE fixed income and data business |
E448102
|
entity |
| Predicate | dataDeliveryMethod |
P114741
|
FINISHED |
| Object | API |
—
|
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: API | Statement: [ICE fixed income and data business, dataDeliveryMethod, API]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataDeliveryMethod Context triple: [ICE fixed income and data business, dataDeliveryMethod, API]
-
A.
deliveryType
Indicates the method or mode by which a product, service, or item is delivered or fulfilled.
-
B.
deliveryTechnology
chosen
Indicates the method or system used to deliver a product, service, or content from a provider to a recipient.
-
C.
ballDeliveryMethod
Indicates the manner or technique by which a ball is delivered, passed, or thrown from one entity to another.
-
D.
deliveryModelOf
Indicates that one entity functions as the delivery model or mechanism through which another entity (such as a service, product, or program) is provided or made available.
-
E.
deliverySystem
Indicates a system, method, or mechanism by which something (such as a product, service, or substance) is transported, distributed, or conveyed from a source to a recipient.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4a30ad8748190b28d3e8b5afab2ef |
completed | April 19, 2026, 9:40 a.m. |
| PD | Predicate disambiguation | batch_69e3d8ec2f6881909d7f54b878cbed37 |
completed | April 18, 2026, 7:18 p.m. |
Created at: April 10, 2026, 10:20 a.m.