Triple
T32279959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo spacecraft CSM-111 |
E824661
|
entity |
| Predicate | missionPartnerCountry |
P51089
|
FINISHED |
| Object | Soviet Union |
—
|
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: Soviet Union | Statement: [Apollo spacecraft CSM-111, missionPartnerCountry, Soviet Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionPartnerCountry Context triple: [Apollo spacecraft CSM-111, missionPartnerCountry, Soviet Union]
-
A.
countryPartner
Indicates a formal partnership relationship between two countries, such as cooperation, alliance, or strategic collaboration.
-
B.
mainTradingPartnerCountry
Indicates the country that serves as the primary trading partner for a given entity, based on the largest or most significant volume of trade.
-
C.
portLeasePartnerCountry
Indicates that a country is a partner in a lease agreement for the use or operation of a port.
-
D.
internationalPartners
Indicates that two or more entities are engaged in a formal or recognized partnership that crosses national boundaries.
-
E.
partnerNation
chosen
Indicates that one entity is recognized as a collaborating or allied nation in relation to another entity.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c1bb5f248190834161b5a6ba1ece |
completed | May 3, 2026, 3:32 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:43 a.m.