Triple
T10460982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lincoln & Herndon |
E246672
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | legal partnership |
C16809
|
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: legal partnership Context triple: [Lincoln & Herndon, instanceOf, legal partnership]
-
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.
limited partnership
A limited partnership is a business structure in which at least one general partner manages the business and bears unlimited liability, while one or more limited partners contribute capital and have liability limited to their investment with no role in day-to-day management.
-
C.
legal relationship
A legal relationship is a formally recognized connection between parties that creates specific rights, duties, and obligations enforceable under the law.
-
D.
business partnership
chosen
A business partnership is a formal arrangement in which two or more individuals or entities share ownership, responsibilities, risks, and profits in operating a business.
-
E.
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.
- 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_69d381c16c248190a2fe5b471e584e9c |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:19 p.m.