Triple
T395498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voyager 2 |
E8973
|
entity |
| Predicate | crossedHeliopause |
P8101
|
FINISHED |
| Object | 2018-11-05 |
—
|
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: 2018-11-05 | Statement: [Voyager 2, crossedHeliopause, 2018-11-05]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossedHeliopause Context triple: [Voyager 2, crossedHeliopause, 2018-11-05]
-
A.
hasHeliosphere
Indicates that an object possesses a surrounding region of space dominated by its own stellar wind and magnetic field, known as a heliosphere.
-
B.
crossedBy
Indicates that one entity (typically a path, line, or boundary) is intersected or traversed by another entity.
-
C.
enteredInterstellarSpaceDate
chosen
Indicates the date on which an object or entity crossed the boundary of its originating stellar system and entered interstellar space.
-
D.
crossesSectionOf
Indicates that one entity passes through or over a specific segment or portion of another entity.
-
E.
crossesBetween
Indicates that one entity passes from one side of a second entity to the other, traversing the space between two reference points or boundaries associated with that second 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec792dd081909b6b18a854139f8c |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96bd3848190a66ca14dfbd26da5 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.