Triple
T35561170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009-071A |
E1027638
|
entity |
| Predicate | hasCOSPARId |
P18899
|
FINISHED |
| Object | 2009-071A |
—
|
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: 2009-071A | Statement: [2009-071A, hasCOSPARId, 2009-071A]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCOSPARId Context triple: [2009-071A, hasCOSPARId, 2009-071A]
-
A.
cosparId
chosen
Indicates that an entity is associated with a specific COSPAR (Committee on Space Research) identifier used to uniquely label space objects or missions.
-
B.
namedForSpacecraft
Indicates that one entity is named after, or in honor of, a specific spacecraft.
-
C.
onSameSpacecraftAs
Indicates that two entities are located on and traveling with the same spacecraft at the same time.
-
D.
associatedWithSpacecraft
Indicates a relationship in which an entity is connected or related in some way to a particular spacecraft, such as by operation, design, mission, or support role.
-
E.
spacecraftSerialNumber
Indicates the unique identifying serial number assigned to a specific spacecraft.
- 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:04 p.m.