Triple
T18329725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Submillimeter Array |
E439106
|
entity |
| Predicate | hasPrimaryScienceGoal |
P1415
|
FINISHED |
| Object | study of the cold universe |
—
|
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: study of the cold universe | Statement: [Submillimeter Array, hasPrimaryScienceGoal, study of the cold universe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryScienceGoal Context triple: [Submillimeter Array, hasPrimaryScienceGoal, study of the cold universe]
-
A.
scienceGoals
Indicates the objectives or intended outcomes that guide and justify a scientific activity, project, or investigation.
-
B.
hasResearchGoal
Indicates that an entity has a specific research objective, aim, or target it is pursuing or designed to address.
-
C.
hasPrimaryGoal
chosen
Indicates that an entity’s main or most important objective is the specified goal.
-
D.
hasScientificInterestIn
Indicates that one entity holds a scientific curiosity, concern, or research focus directed toward another entity.
-
E.
isExoplanetSearchTarget
Indicates that an astronomical object has been identified as a suitable target for searching for exoplanets.
- 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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50ec900808190bc4468270e0957c1 |
completed | April 19, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:36 a.m.