Triple
T9627733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Event Horizon Telescope |
E232512
|
entity |
| Predicate | capturedImageOf |
P38871
|
FINISHED |
| Object | supermassive black hole in galaxy M87 |
—
|
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: supermassive black hole in galaxy M87 | Statement: [Event Horizon Telescope, capturedImageOf, supermassive black hole in galaxy M87]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capturedImageOf Context triple: [Event Horizon Telescope, capturedImageOf, supermassive black hole in galaxy M87]
-
A.
capturedBy
Indicates that one entity has been seized, taken into control, or otherwise apprehended by another entity.
-
B.
capturedUsing
Indicates that something was recorded, obtained, or documented by means of a specified tool, method, or device.
-
C.
capturedAs
Indicates that one entity has been taken into custody or control by another entity, typically as a prisoner or target.
-
D.
imagedBy
chosen
Indicates that something is captured, recorded, or represented in an image created by a particular imaging device, method, or agent.
-
E.
imagedIn
Indicates that one entity appears within or is depicted in an image associated with 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_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. |
Created at: March 30, 2026, 8:10 p.m.