Triple
T26629265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRDIS |
E668446
|
entity |
| Predicate | isSubInstrumentOf |
P73603
|
FINISHED |
| Object | SPHERE exoplanet imager |
—
|
NE NERFINISHED |
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: SPHERE exoplanet imager | Statement: [IRDIS, isSubInstrumentOf, SPHERE exoplanet imager]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSubInstrumentOf Context triple: [IRDIS, isSubInstrumentOf, SPHERE exoplanet imager]
-
A.
isInstrumentFor
Indicates that something is used as a tool or means to perform a particular action or achieve a specific outcome.
-
B.
parentInstrument
chosen
Indicates that one instrument serves as the broader, containing, or originating instrument from which another, more specific or derived instrument is related.
-
C.
relatesToInstrument
Indicates a relationship where one entity is associated with, involves, or makes use of a particular instrument or tool.
-
D.
usedAsInstrumentBy
Indicates that one entity functions as a tool, means, or instrument through which another entity performs an action or achieves an effect.
-
E.
studiedByInstrument
Indicates that something is examined, measured, or analyzed through the use of a specific instrument or device.
- 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_69ee9cff507c819092b95bf7219a702e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 2:24 a.m.