Triple
T11692588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Act Agreements |
E277904
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | partnership mechanism |
C29716
|
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: partnership mechanism Context triple: [Space Act Agreements, instanceOf, partnership mechanism]
-
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.
strategic partnership
A strategic partnership is a long-term, collaborative relationship between two or more independent organizations that align resources, capabilities, and objectives to achieve mutually beneficial competitive advantages they could not easily attain alone.
-
C.
labor–management partnership
A labor–management partnership is a collaborative relationship between employees (often through unions) and employers designed to jointly address workplace issues, improve organizational performance, and enhance job quality through shared decision-making and problem-solving.
-
D.
community-based mechanism
A community-based mechanism is a locally driven process or structure through which community members collectively identify, decide on, and implement actions to address shared needs or manage common resources.
-
E.
human partnership
A human partnership is a collaborative relationship between two or more people who share goals, responsibilities, and mutual support to achieve common outcomes.
- F. None of above. chosen
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.