Triple
T24818492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyperion |
E620989
|
entity |
| Predicate | closeFlybyBy |
P28276
|
FINISHED |
| Object | Cassini on 2005-09-26 |
—
|
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: Cassini on 2005-09-26 | Statement: [Hyperion, closeFlybyBy, Cassini on 2005-09-26]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: closeFlybyBy Context triple: [Hyperion, closeFlybyBy, Cassini on 2005-09-26]
-
A.
flybyOf
chosen
Indicates that one entity passes close to another in space without stopping, typically as part of an observational or transit maneuver.
-
B.
flybyPhase
Indicates the specific stage or segment of a spacecraft’s trajectory during a flyby of a celestial body.
-
C.
firstFlybyBy
Indicates that one entity was the spacecraft, probe, or mission that performed the first flyby of another entity (such as a celestial body or target).
-
D.
flybyAgency
Indicates the agency or organization responsible for conducting or managing a spacecraft’s flyby of a target body.
-
E.
flybyCount
Indicates the number of times one object or entity passes close by another along its trajectory without stopping or entering into a stable orbit or interaction.
- 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_69e2fabfd4648190bd0e5c7f4dbb6cab |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:04 a.m.