Triple
T16692602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standard Cygnus |
E405629
|
entity |
| Predicate | firstISSVisit |
P39482
|
FINISHED |
| Object | Orb-D1 demonstration mission |
—
|
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: Orb-D1 demonstration mission | Statement: [Standard Cygnus, firstISSVisit, Orb-D1 demonstration mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstISSVisit Context triple: [Standard Cygnus, firstISSVisit, Orb-D1 demonstration mission]
-
A.
wasFirstVisitedBy
Indicates that a particular entity was initially reached, discovered, or visited by another specified entity before any others.
-
B.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
-
C.
firstReachedDate
Indicates the date on which a particular entity first achieved, accessed, or arrived at a specified state, location, or milestone.
-
D.
firstISSRendezvous
chosen
Indicates that the event represents the first successful rendezvous (meeting or docking) with the International Space Station for the entities involved.
-
E.
firstInvocationDate
Indicates the date on which the entity was first invoked, used, or called for the first time.
- 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_69d8838c28748190b3f5967c743940ab |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37eaacb948190954231c9e97a4adf |
completed | April 18, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69e319bc73908190a0e38bc926b31f10 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.