Triple
T22555089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Styx (moon) |
E557658
|
entity |
| Predicate | flybyDateBy |
P22034
|
FINISHED |
| Object | New Horizons on 2015-07-14 |
—
|
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: New Horizons on 2015-07-14 | Statement: [Styx (moon), flybyDateBy, New Horizons on 2015-07-14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: flybyDateBy Context triple: [Styx (moon), flybyDateBy, New Horizons on 2015-07-14]
-
A.
flybyDate
chosen
Indicates the date on which one object passes close to another in a flyby encounter.
-
B.
flybyOf
Indicates that one entity passes close to another in space without stopping, typically as part of an observational or transit maneuver.
-
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.
firstFlybyDate
Indicates the date on which an object or mission first performed a flyby of a target body or location.
-
E.
flybyAgency
Indicates the agency or organization responsible for conducting or managing a spacecraft’s flyby of a target body.
- 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_69e11e59db848190b4272ecd2b690ffd |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f78d8288190871d54db0a7f454b |
completed | April 29, 2026, 1:31 a.m. |
| PD | Predicate disambiguation | batch_69e898cb3fb48190add6ab24a2df5822 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:52 p.m.