Triple
T26629234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAXO |
E668445
|
entity |
| Predicate | hostInstrumentMode |
P161945
|
FINISHED |
| Object | SPHERE/ZIMPOL |
—
|
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/ZIMPOL | Statement: [SAXO, hostInstrumentMode, SPHERE/ZIMPOL]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostInstrumentMode Context triple: [SAXO, hostInstrumentMode, SPHERE/ZIMPOL]
-
A.
hostInstrument
Indicates that one entity serves as the instrument or platform that hosts, carries, or enables another entity or process.
-
B.
hostsInstrument
Indicates that one entity serves as the location, platform, or environment in which an instrument is installed, operated, or utilized.
-
C.
instrumentMode
Indicates the manner, setting, or operational mode in which an instrument is used to perform an action or measurement.
-
D.
parentInstrument
Indicates that one instrument serves as the broader, containing, or originating instrument from which another, more specific or derived instrument is related.
-
E.
mainInstrumentFeatures
Indicates that the specified features characterize or describe the main instrument involved in an event or context.
- F. None of above. chosen
Provenance (4 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_69f62081136c81909de8090b1d6c1ac5 |
completed | May 2, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
| PDg | Predicate description generation | batch_69f61fd5442081908ca677a9c81dcb3f |
completed | May 2, 2026, 4:01 p.m. |
Created at: April 27, 2026, 2:24 a.m.