Triple
T13179296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X-Ray Telescope |
E313682
|
entity |
| Predicate | detectsFrom |
P53467
|
FINISHED |
| Object | black holes |
—
|
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: black holes | Statement: [X-Ray Telescope, detectsFrom, black holes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: detectsFrom Context triple: [X-Ray Telescope, detectsFrom, black holes]
-
A.
detected
chosen
Indicates that an entity has observed, identified, or discovered the presence or occurrence of another entity or event.
-
B.
requiresDetectionOf
Indicates that one entity can only occur, be valid, or proceed if another entity has first been detected or identified.
-
C.
detectorType
Indicates the specific kind or category of detector associated with an entity or measurement.
-
D.
canDetermine
Indicates that one entity has the ability or authority to find out, establish, or decide the state, value, or outcome of another entity or situation.
-
E.
canRecognize
Indicates that one entity has the ability to identify or distinguish another entity based on its features or characteristics.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:14 p.m.