Triple
T17459898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HEOS-2 |
E425124
|
entity |
| Predicate | precededBy |
P97
|
FINISHED |
| Object | HEOS-1 |
—
|
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: HEOS-1 | Statement: [HEOS-2, precededBy, HEOS-1]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HEOS-1 Context triple: [HEOS-2, precededBy, HEOS-1]
-
A.
HEOS-1
chosen
HEOS-1 was a European Space Research Organisation scientific satellite launched in 1968 to study Earth's magnetosphere and interplanetary space.
-
B.
HEOS-2
HEOS-2 was a European scientific satellite launched in 1972 to study Earth's magnetosphere and interplanetary space.
-
C.
HEOS bus
The HEOS bus is a standardized spacecraft platform developed for the Highly Eccentric Orbit Satellite missions, providing the structural, power, and control systems for HEOS-1 and related satellites.
-
D.
HÖS
HÖS is the German vehicle registration code assigned to the Erlangen-Höchstadt district in Bavaria.
-
E.
Sonos One
Sonos One is a compact wireless smart speaker known for its high-quality sound and built-in voice assistant support for multi-room audio systems.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451444e008190944d9668d4d901fa |
completed | April 19, 2026, 3:51 a.m. |
Created at: April 10, 2026, 5:47 a.m.