Triple
T1783621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragonfly |
E39340
|
entity |
| Predicate | scienceInstruments |
P13781
|
FINISHED |
| Object | mass spectrometer |
—
|
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: mass spectrometer | Statement: [Dragonfly, scienceInstruments, mass spectrometer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scienceInstruments Context triple: [Dragonfly, scienceInstruments, mass spectrometer]
-
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.
observatoryType
Indicates the specific kind or category of observatory associated with an entity.
-
C.
spectrographType
Indicates the specific kind or category of spectrograph associated with an instrument or observation.
-
D.
scienceGoals
Indicates the objectives or intended outcomes that guide and justify a scientific activity, project, or investigation.
-
E.
telescopeUsed
Indicates that a particular telescope was employed or utilized to perform an observation or related activity.
- 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_69a88630519c8190a17addd83c4a3ef4 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab75457e54819096b8c6ae8c65550c |
completed | March 7, 2026, 12:45 a.m. |
| PD | Predicate disambiguation | batch_69aa61d165688190924962a98e07ff69 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.