Triple
T9627762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Event Horizon Telescope |
E232512
|
entity |
| Predicate | dataVolumePerCampaign |
P89341
|
FINISHED |
| Object | petabytes of data |
—
|
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: petabytes of data | Statement: [Event Horizon Telescope, dataVolumePerCampaign, petabytes of data]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataVolumePerCampaign Context triple: [Event Horizon Telescope, dataVolumePerCampaign, petabytes of data]
-
A.
dataAggregation
Indicates the process by which multiple data points or datasets are combined into a summarized or consolidated form.
-
B.
numberOfCampaignsApprox
Indicates an approximate count of campaigns associated with or relevant to a given entity.
-
C.
dataRateGeneration
Indicates the rate at which data is produced or generated over time in a given context.
-
D.
dataRate
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
E.
historicalVolume
Indicates a relationship where a volume (such as a book, record, or dataset) pertains to or documents historical information or events.
- F. None of above. chosen
Provenance (4 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_69ca848793ec8190a93a12383a754dc0 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9afeb64c8190be91024c2e9039d3 |
completed | April 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69ccd5acfa5c8190aaba3cf548723604 |
completed | April 1, 2026, 8:22 a.m. |
| PDg | Predicate description generation | batch_69ccd93fc45c8190a823305e461e581d |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:10 p.m.