Triple
T806571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MagE |
E17449
|
entity |
| Predicate | scienceUse |
P13781
|
FINISHED |
| Object | stellar spectroscopy |
—
|
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: stellar spectroscopy | Statement: [MagE, scienceUse, stellar spectroscopy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scienceUse Context triple: [MagE, scienceUse, stellar spectroscopy]
-
A.
scientificInstruments
chosen
Indicates that one entity is a scientific instrument used by, associated with, or relevant to another entity in the context of scientific measurement or research.
-
B.
scienceGoals
Indicates the objectives or intended outcomes that guide and justify a scientific activity, project, or investigation.
-
C.
usedResearchFrom
Indicates that one entity based its work, findings, or outputs on research conducted or provided by another entity.
-
D.
scientificConsensus
Indicates that there is broad agreement among qualified experts or authoritative sources that a particular claim, finding, or theory is valid.
-
E.
positionOnScience
Indicates the stance, viewpoint, or attitude an entity holds regarding science or scientific matters.
- 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_69a4937ae8a08190b5084a03d532b30e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ac07fedc8190ab05595f25c1792f |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7221c081908068e66fe720f26d |
completed | March 1, 2026, 9:06 p.m. |
Created at: March 1, 2026, 7:38 p.m.