Triple
T11692589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Act Agreements |
E277904
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collaborative agreement |
C23224
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: collaborative agreement Context triple: [Space Act Agreements, instanceOf, collaborative agreement]
-
A.
partnership agreement
A partnership agreement is a legally binding contract between two or more parties that defines their business relationship, including ownership shares, roles, responsibilities, profit and loss distribution, and procedures for decision-making and dispute resolution.
-
B.
collaborative research and development agreement
chosen
A collaborative research and development agreement is a contract between two or more parties that defines how they will jointly conduct R&D activities, share resources, allocate intellectual property rights, and manage risks and responsibilities.
-
C.
political agreement
A political agreement is a negotiated understanding or formal accord between political actors or entities that defines shared commitments, terms, and responsibilities on specific issues or policies.
-
D.
collaborative project
A collaborative project is a coordinated effort in which multiple individuals or groups work together, sharing responsibilities, resources, and expertise to achieve a common goal.
-
E.
antitrust agreement
An antitrust agreement is a formal or informal arrangement between two or more independent economic entities that coordinates their competitive behavior in a way that may restrict competition, such as fixing prices, limiting output, or dividing markets.
- F. None of above.
Provenance (1 batch)
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_69d6aafe02d881909900d54ad7d4af84 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:40 p.m.