Triple
T56363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SETI |
E1114
|
entity |
| Predicate | dataSource |
P409
|
FINISHED |
| Object | radio telescopes |
—
|
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: radio telescopes | Statement: [SETI, dataSource, radio telescopes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataSource Context triple: [SETI, dataSource, radio telescopes]
-
A.
source
chosen
Indicates that something originates from, is derived from, or is provided by a particular entity or location.
-
B.
dataModel
Indicates a relationship where an entity defines, uses, or is structured according to a specific data model or schema.
-
C.
dataStorage
Indicates a relationship where one entity serves as a repository that holds, retains, or maintains data for another entity or process.
-
D.
sourceRegion
Indicates the geographic or spatial region from which something originates or is derived.
-
E.
dataUse
Indicates how data is intended to be accessed, processed, or applied within a particular context or activity.
- 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_69a248adc5b48190aa8db9fb092fb28a |
completed | Feb. 28, 2026, 1:45 a.m. |
| NER | Named-entity recognition | batch_69a24b915c9881908c798f4dacb39f1d |
completed | Feb. 28, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69a24ac6799c8190b508933acc0a4c7d |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:50 a.m.