Triple
T12254788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euclid spacecraft |
E292070
|
entity |
| Predicate | VISInstrumentFullName |
P12711
|
FINISHED |
| Object | Visible Instrument |
—
|
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: Visible Instrument | Statement: [Euclid spacecraft, VISInstrumentFullName, Visible Instrument]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: VISInstrumentFullName Context triple: [Euclid spacecraft, VISInstrumentFullName, Visible Instrument]
-
A.
instrumentAbbreviation
Indicates that one entity is an abbreviation or shortened form used to represent a particular instrument in a given context.
-
B.
describesInstrument
Indicates that one entity specifies or characterizes the instrument or tool used by another entity to perform an action.
-
C.
musicInstrumentation
Indicates the specific instruments or instrumental forces used to perform a piece of music.
-
D.
typeOfInstrument
chosen
Indicates the specific kind or category of instrument associated with an entity.
-
E.
parentInstrument
Indicates that one instrument serves as the broader, containing, or originating instrument from which another, more specific or derived instrument is related.
- 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91d38ee10819093ed41d2954bf4ef |
completed | April 10, 2026, 3:54 p.m. |
| PD | Predicate disambiguation | batch_69d91c46dcd88190a263db30804bff36 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.