Triple
T3816195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clark/Hunt/Smoot |
E84260
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | construction joint venture |
C14074
|
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: construction joint venture Context triple: [Clark/Hunt/Smoot, instanceOf, construction joint venture]
-
A.
construction industry partnership
chosen
A construction industry partnership is a collaborative alliance between contractors, suppliers, designers, and other stakeholders formed to jointly plan, finance, and deliver construction projects more efficiently and profitably.
-
B.
building society
A building society is a member-owned financial institution that primarily offers savings accounts and mortgage lending, operating on a mutual, not-for-profit basis.
-
C.
construction and trading company
A construction and trading company is a business entity that both executes building and infrastructure projects and engages in the procurement, sale, and distribution of construction-related materials, equipment, or goods.
-
D.
automotive joint venture
An automotive joint venture is a strategic business arrangement in which two or more companies collaborate to develop, produce, or distribute vehicles or related technologies while sharing resources, risks, and profits.
-
E.
business consortium
A business consortium is a collaborative association of independent companies that pool resources, expertise, or capital to pursue shared objectives, projects, or market opportunities while retaining their individual autonomy.
- 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_69aed931f5908190be2c07af66d4df25 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:17 p.m.