Triple
T9807881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo–Soyuz Docking Module |
E238196
|
entity |
| Predicate | agreementContext |
P9252
|
FINISHED |
| Object | developed under 1972 US–USSR space cooperation agreement |
—
|
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: developed under 1972 US–USSR space cooperation agreement | Statement: [Apollo–Soyuz Docking Module, agreementContext, developed under 1972 US–USSR space cooperation agreement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: agreementContext Context triple: [Apollo–Soyuz Docking Module, agreementContext, developed under 1972 US–USSR space cooperation agreement]
-
A.
agreement
Indicates that two or more parties mutually consent to and accept shared terms, conditions, or understandings.
-
B.
aimOfAgreement
Indicates the intended purpose or objective that an agreement is designed to achieve.
-
C.
involvedAgreement
Indicates that an entity participates in, is a party to, or is otherwise associated with a specific agreement or contract.
-
D.
agreementOutcome
Indicates the result or consequence that follows from reaching or failing to reach an agreement between parties.
-
E.
basedOnAgreementWith
chosen
Indicates that something exists, is done, or is determined on the basis of a prior agreement or accord between the involved parties.
- 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_69ca84defac48190abc1148804f184c1 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdab7ddaac8190a5584a5c863fbaa3 |
completed | April 1, 2026, 11:34 p.m. |
| PD | Predicate disambiguation | batch_69cd03dd2da881909052fbf29736a773 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:29 p.m.