Triple
T3587589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESO 3.6 m Telescope |
E75947
|
entity |
| Predicate | primaryScienceTarget |
P37042
|
FINISHED |
| Object | nearby stars |
—
|
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: nearby stars | Statement: [ESO 3.6 m Telescope, primaryScienceTarget, nearby stars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryScienceTarget Context triple: [ESO 3.6 m Telescope, primaryScienceTarget, nearby stars]
-
A.
primaryScience
Indicates that one entity serves as the main or principal scientific focus, discipline, or domain associated with another entity.
-
B.
primaryScienceUse
chosen
Indicates that something serves as the main or principal scientific purpose or application of an entity or resource.
-
C.
primaryScienceBand
Indicates that one entity serves as the main or principal science band associated with another entity.
-
D.
primarySchool
Indicates that one entity serves as the primary (elementary) school attended by, associated with, or designated for the other entity.
-
E.
secondaryScienceBand
Indicates that an entity is associated with a secondary or additional science-related band or spectral range beyond its primary one.
- 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_69ad85d6dc3c8190b491b79b83e25461 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc13a11608190a23d76efc1b50e3c |
completed | March 8, 2026, 6:34 p.m. |
| PD | Predicate disambiguation | batch_69adb839b4e08190b1c0d611cccb11ae |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:22 p.m.