Triple
T37104738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dawodang depression |
E918810
|
entity |
| Predicate | astronomySiteType |
P7248
|
FINISHED |
| Object | radio telescope site |
—
|
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 telescope site | Statement: [Dawodang depression, astronomySiteType, radio telescope site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: astronomySiteType Context triple: [Dawodang depression, astronomySiteType, radio telescope site]
-
A.
astronomySiteSince
Indicates that an entity has held the status or function of an astronomy-related site starting from a specified point in time.
-
B.
astronomyDiscoverySiteOf
Indicates the location where an astronomical object, phenomenon, or feature was first discovered or identified.
-
C.
astronomicalType
Indicates the classification relationship that specifies what kind of astronomical object or phenomenon something is (e.g., star, galaxy, planet).
-
D.
observatoryType
chosen
Indicates the specific kind or category of observatory associated with an entity.
-
E.
astronomyPlatform
Indicates a relationship where something serves as a platform, environment, or system specifically used for conducting, supporting, or presenting astronomy-related activities or data.
- 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_69f76e9b99c8819096164b21ff5bd996 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb344c60f8819090f2e21e1e61d621 |
completed | May 6, 2026, 12:30 p.m. |
| PD | Predicate disambiguation | batch_69fb2f642db08190b562725502c74ea6 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:14 p.m.