Triple
T26148333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parkes |
E659741
|
entity |
| Predicate | observatoryRole |
P38765
|
FINISHED |
| Object | radio astronomy research |
—
|
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 astronomy research | Statement: [Parkes, observatoryRole, radio astronomy research]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observatoryRole Context triple: [Parkes, observatoryRole, radio astronomy research]
-
A.
telescopeRole
chosen
Indicates the functional role or purpose that a telescope serves within an observation, system, or activity.
-
B.
observatoryOperator
Indicates that one entity operates, manages, or runs an observatory facility for another entity or in an official capacity.
-
C.
observatoryFor
Indicates that something serves as an observatory specifically dedicated to observing, studying, or monitoring a particular target or subject.
-
D.
observatory
Indicates a relationship where a facility or structure is used to observe, monitor, or study objects or phenomena, typically in astronomy or atmospheric science.
-
E.
astronomicalRole
Indicates the functional or positional role that one astronomical object or entity has in relation to another (e.g., star vs. planet, primary vs. satellite).
- 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_69ee5bc496a88190af7deb7ab5e081de |
completed | April 26, 2026, 6:39 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f63182f1408190bddc1214fcbd6145 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 26, 2026, 8:23 p.m.