Triple
T742997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vanguard 1 |
E15283
|
entity |
| Predicate | nssdcId |
P3732
|
FINISHED |
| Object | 1958-002B |
—
|
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: 1958-002B | Statement: [Vanguard 1, nssdcId, 1958-002B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nssdcId Context triple: [Vanguard 1, nssdcId, 1958-002B]
-
A.
spaceAgency
Indicates that one entity is a space agency that operates, manages, or oversees space-related missions, programs, or activities on behalf of the other entity.
-
B.
GNISID
Indicates that an entity is associated with a specific identifier from the U.S. Geographic Names Information System (GNIS), uniquely linking it to an official geographic feature record.
-
C.
spacecraftLaunchAssociatedWith
Indicates a relationship where a spacecraft launch is connected or linked to another event, object, or entity involved in or affected by that launch.
-
D.
identifierFor
chosen
Indicates that one entity serves as a unique identifying label or code for another entity.
-
E.
observatoryCode
Indicates a code that uniquely identifies the observatory associated with an observation or measurement.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a60f92d08190a4f44c5b4d068ab5 |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a4fdaaf48190985f62acfc069508 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.