Triple
T18541335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UGC 12713 |
E453105
|
entity |
| Predicate | observedInRadioWavelengths |
P38137
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [UGC 12713, observedInRadioWavelengths, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observedInRadioWavelengths Context triple: [UGC 12713, observedInRadioWavelengths, true]
-
A.
hasObservationWavelength
Indicates the specific wavelength at which an observation or measurement is made or recorded.
-
B.
observingBand
chosen
Indicates that an entity is observing or monitoring another entity using a specific spectral band or frequency range.
-
C.
otherGreatObservatories
Indicates a relationship in which an entity is associated with, compared to, or grouped among other major observatories of similarly high importance or capability.
-
D.
observationalVisibility
Indicates that one entity is able to observe or visually perceive another entity under given conditions.
-
E.
visibleInSmallTelescope
Indicates that the object can be seen using a small telescope under typical observing conditions.
- 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_69d8d387b5548190aa030dad2cb4947e |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e534b749b88190ad03b26bee3c89df |
completed | April 19, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69e469e274a48190a570b25cfef4d890 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:37 a.m.