Triple
T25750441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CONTOUR |
E648456
|
entity |
| Predicate | plannedFlyby |
P28276
|
FINISHED |
| Object | Comet 73P/Schwassmann–Wachmann 3 |
—
|
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: Comet 73P/Schwassmann–Wachmann 3 | Statement: [CONTOUR, plannedFlyby, Comet 73P/Schwassmann–Wachmann 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedFlyby Context triple: [CONTOUR, plannedFlyby, Comet 73P/Schwassmann–Wachmann 3]
-
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.
flybyOrOrbiter
Indicates that one entity performs a close pass or maintains an orbital trajectory around another entity without landing on it.
-
C.
flybyPhase
Indicates the specific stage or segment of a spacecraft’s trajectory during a flyby of a celestial body.
-
D.
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).
-
E.
flybyDate
Indicates the date on which one object passes close to another in a flyby encounter.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f627aedf548190bc9f53c8a2d67b50 |
completed | May 2, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69f623a4e1048190bbb8dd1253fdcee9 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 22, 2026, 4:34 a.m.