Triple
T6204833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parker Solar Probe |
E138720
|
entity |
| Predicate | firstSolarEncounter |
P68909
|
FINISHED |
| Object | 2018-10-31 |
—
|
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-10-31 | Statement: [Parker Solar Probe, firstSolarEncounter, 2018-10-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSolarEncounter Context triple: [Parker Solar Probe, firstSolarEncounter, 2018-10-31]
-
A.
firstEncounteredBy
Indicates that one entity is the person or agent who initially discovered, met, or came across the other entity for the first time.
-
B.
firstCRSMission
Indicates that the referenced mission is the first mission conducted under the CRS (Commercial Resupply Services) program or contract.
-
C.
firstISSRendezvous
Indicates that the event represents the first successful rendezvous (meeting or docking) with the International Space Station for the entities involved.
-
D.
firstMission
Indicates that an entity is undertaking or associated with its initial mission or assignment in a given context.
-
E.
firstContactContext
Indicates the circumstances or situation under which two entities first came into contact or interacted.
- F. None of above. chosen
Provenance (4 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_69c008acbea48190991c6b834bb45d65 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0626d96ec8190816c00c44668177d |
completed | March 22, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69c055fdea3c81908f5d910f0d36234a |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056c965ac8190b938502fa8c74e1b |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:20 p.m.