Triple
T17245525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Low Frequency Instrument |
E418614
|
entity |
| Predicate | hostSpacecraftInstanceOf |
P104772
|
FINISHED |
| Object | space observatory |
—
|
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: space observatory | Statement: [Low Frequency Instrument, hostSpacecraftInstanceOf, space observatory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostSpacecraftInstanceOf Context triple: [Low Frequency Instrument, hostSpacecraftInstanceOf, space observatory]
-
A.
hostSpacecraft
Indicates that one entity serves as the platform or carrier on which another spacecraft is mounted, accommodated, or operated.
-
B.
isOnSpacecraftType
chosen
Indicates that one entity is currently aboard or assigned to a spacecraft of a specified type.
-
C.
mainSpacecraft
Indicates that one spacecraft is designated as the primary or principal spacecraft in relation to another entity or context.
-
D.
servicedSpacecraft
Indicates that one entity has performed maintenance or support operations on a spacecraft.
-
E.
hostSpacecraftOperator
Indicates that one entity operates or manages the spacecraft that is being hosted or carried by another entity.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e23b8948190870d0e6b4e55b4e3 |
completed | April 19, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.